Service advisor accounts for remote service monitoring of a vehicle

ABSTRACT

Methods and systems are provided. One method includes receiving a request, at a server, to establish an advisor account for a vehicle associated with a user account. The request identifies a service entity and a vehicle service to be assigned to the service entity. The service entity is configured to receive said diagnostics data of the vehicle. The advisor account is associated to the service entity. Programming data is sent to the vehicle for use by a computer of the vehicle to identify select diagnostics data that relates to the vehicle service and to make accessible said select diagnostics data to the advisor account. The advisor account is made accessible to the service entity subsequent to establishing of the advisor account. The server receives select diagnostics data from the vehicle regarding the vehicle service, and the select diagnostics data is accessible for viewing and/or processing by a device of the service entity. The select diagnostics data produces updates that identify characteristics or changes in characteristics that relate to the vehicle service, and the server uses the identified characteristics or changes in characteristics to trigger a notification to the service entity regarding a problem or potential problem regarding the vehicle service.

CLAIM OF PRIORITY

The present application is a continuation of U.S. application Ser. No.15/696,618 filed on Sep. 6, 2017, entitled “Methods and Systems forAssigning Service Advisor Accounts for Vehicle Systems and CloudProcessing” which is a continuation of U.S. application Ser. No.15/615,812 filed on Jun. 6, 2017 (now U.S. Pat. No. 9,818,088, issued onNov. 14, 2017) entitled “Vehicles and Cloud Systems for ProvidingRecommendations to Vehicle Users to Handle Alerts Associated with theVehicle” which is a continuation of U.S. patent application Ser. No.14/176,138, filed on Feb. 9, 2014, (now U.S. Pat. No. 9,697,503, issuedon Jul. 4, 2017) entitled “Methods and Systems for ProvidingRecommendations to Vehicle users to Handle Alerts Associated with theVehicle and A Bidding Market Place for Handling Alerts/Service of theVehicle,” which claims priority of U.S. Provisional Patent ApplicationNo. 61/896,007, filed on Oct. 25, 2013, entitled “Methods and Systemsfor Intelligent Software, Data, Job, Bid and Offer Transfer betweenEntities though a Vehicle Service Marketplace,” which are hereinincorporated by reference.

U.S. application Ser. No. 15/696,618 is a continuation of U.S.application Ser. No. 15/607,418 filed on May 26, 2017, entitled“Vehicles and Cloud Systems for Assigning Temporary E-Keys to Access useof a Vehicle,” which is a continuation of U.S. application Ser. No.14/063,638, filed on Oct. 25, 2013 (now U.S. Pat. No. 9,189,900, issuedon Oct. 28, 2015), entitled “Methods and Systems for Assigning e-Keys toUsers to Access and Drive Vehicles,” which are incorporated byreference.

U.S. patent application Ser. No. 14/176,138 is a continuation-in-part ofU.S. patent application Ser. No. 14/063,837, filed on Oct. 25, 2013,(now U.S. Pat. No. 9,139,091, issued on Sep. 22, 2015) entitled “Methodsand Systems for Setting and/or Assigning Advisor Accounts to Entitiesfor Specific Vehicle Aspects and Cloud Management of Advisor Accounts,”which claims priority, as a continuation-in-part of U.S. applicationSer. No. 13/842,158, filed on Mar. 15, 2013, (now U.S. Pat. No.9,229,905, issued on Jan. 5, 2016) entitled “Methods and Systems forDefining Vehicle User Profiles and Managing User Profiles via CloudSystems and Applying Learned Settings to User Profiles”, which claimedpriority of U.S. Provisional Patent Application No. 61/745,729, filed onDec. 24, 2012, and entitled “Methods And Systems For Electric Vehicle(EV) Charging, Charging Systems, Internet Applications And UserNotifications”, all of which are herein incorporated by reference.

U.S. patent application Ser. No. 14/176,138 is a continuation-in-part ofU.S. application Ser. No. 13/452,882, filed Apr. 22, 2012, (now U.S.Pat. No. 9,123,035, issued on Sep. 1, 2015) and entitled “ElectricVehicle (EV) Range Extending Charge Systems, Distributed Networks OfCharge Kiosks, And Charge Locating Mobile Apps”, which claims priorityto U.S. Provisional Application No. 61/478,436, filed on Apr. 22, 2011,all of which are incorporated herein by reference.

FIELD OF THE EMBODIMENTS

The present invention relates to systems and methods for managing userprofiles for vehicles and exchange of information with cloud-basedprocessing systems.

BACKGROUND

Vehicles, such as motorized vehicles and electric vehicles have beenaround for some time. Vehicles provide a means that enable humans todrive from place to place. In today's world, vehicles have become anindispensable mode of transportation, and provide the freedom to travelat any time of day and for various distances. Vehicles can be publicallyoperated or can be privately owned. Humans most commonly operatevehicles, no matter the type, whether electric or combustion enginebased. In recent years, technology has been advancing to allow forbetter wireless interfacing and networking with vehicles. It is in thiscontext that embodiments of the invention arise.

SUMMARY

The methods, systems and apparatus include electronics of vehicles thatdrive display devices in vehicles and communicate wirelessly withInternet services.

Methods and systems provide access to cloud services over the Internetfor managing a user profile of a vehicle on a cloud processing systemconnected to the Internet. One example method includes receivingrequests to access the user profile to define settings for one or morevehicles. The method includes receiving input for user settings at thevehicle using the cloud processing system. The method includesprocessing the input over time to learn behavior associated with theinput to the use settings. The method includes transmitting settings tothe vehicle to be automatically implemented based on the learnedbehavior. In one example, the profile is associated with a plurality ofvehicle types and the method includes detecting a violation of a settingor an incompatible setting in the profile that is user defined via theuser account. The method can then automatically send a notification to apredefined administrator of the profile. The method being executed by aprocessor.

The profile can be transferred to one or more vehicles, can be set for atemporary period of time, can be set with wireless payment systems, andis accessible over the Internet to accept changes or updates.

In one embodiment, a user can assign an ad advisor account to anyindividual. The Advisor account can be for any duration, and theduration can be set by the user. In one embodiment, the advisor accountcan be assigned to a guest driver of a vehicle. The guest driver can be,for example, a friend, a known individual, a service person, a valetperson or valet service, etc. The creation of an advisor account cantherefore be for a short duration, or long duration, or permanently, oruntil the account is canceled, stopped, revoked, expires, or eliminatedby the person/user that issued or created the advisor account. In oneembodiment, the advisor account can act to provide access to a vehicle.

In one embodiment, a method includes receiving a request, at a server,to establish an advisor account for a vehicle to be associated a useraccount. The request identifies a service entity and a vehicle serviceto be assigned to the service entity. The service entity is configuredto receive said diagnostics data of the vehicle. The advisor account isassociated to the service entity. Programming data is sent to thevehicle for use by a computer of the vehicle to identify selectdiagnostics data that relates to the vehicle service and to makeaccessible said select diagnostics data to the advisor account. Theadvisor account is made accessible to the service entity subsequent toestablishing of the advisor account. The server receives selectdiagnostics data from the vehicle regarding the vehicle service, and theselect diagnostics data is accessible for viewing and/or processing by adevice of the service entity. The select diagnostics data producesupdates that identify characteristics or changes in characteristics thatrelate to the vehicle service, and the server uses the identifiedcharacteristics or changes in characteristics to trigger a notificationto the service entity regarding a problem or potential problem regardingthe vehicle service.

In one embodiment, a method includes receiving a request, at a server,to define an advisor account for a vehicle associated with a useraccount. The request identifies an advisor entity, a vehicle aspect tobe assigned to the advisor entity, and privileges assigned to theadvisor entity for the vehicle aspect. The method further includesgenerating the advisor account for the advisor entity as a sub-accountof the user account that is associated with the vehicle. The methodincludes sending instruction data to the vehicle from the server,wherein the instruction data defines that the vehicle aspect isassociated with the advisor account. The method also includes receivingdata updates, at the server, from the vehicle for the vehicle aspect,from time to time. The data updates are displayable on a user interfacethat is accessible to the advisor entity, the user interface beingrendered by the server that provides access to the advisor account.

In some embodiments, the privileges define a level of access to dataabout the vehicle or remote access of the vehicle via the advisoraccount for the vehicle aspect.

In some embodiments, the user account includes a plurality of advisoraccounts; each advisor account is associated with the vehicle andassigned to different advisor entities for different vehicle aspects,each of the different vehicle aspects being assigned with same ordifferent privileges.

In some embodiments, a vehicle aspect is a part, feature, function,operation or combinations thereof of the vehicle, and each vehicleaspect or multiple vehicle aspects are assignable to the advisor accountwith associated privileges.

In some embodiments, the data updates define characteristics or changesin characteristics of the vehicle aspect.

In some embodiments, the advisor account enables remote access to thevehicle to act upon a feature of the vehicle aspect.

In some embodiments, the method further includes receiving one or morerequest from the user account associated with the vehicle to assign oneor more advisor accounts that are in addition to the advisor account,wherein each of the advisor accounts are associated with differentvehicle aspects of the vehicle.

In some embodiments, the advisor account includes a communicationprotocol to enable a user of the advisor account to provide adviceregarding the vehicle aspect.

In some embodiments, the user of the advisor account, in accordance withthe privileges, is enabled to perform remote diagnostics to provideadditional advice, order parts and schedule appointments.

In some embodiments, the privileges are associated with the vehicleaspect for which the advisor account is defined; the privileges excludeaccess to vehicle aspects not included in the privileges via the advisoraccount.

In some embodiments, driver accounts are defined as sub-accounts to theuser account, the driver accounts define roles that limit or enableaspects of the vehicle.

In some embodiments, advisor account access and details are enabled viaa website or an application, the website or application provide userinterface screens for creating accounts, editing accounts and viewingactivity and history regarding the accounts.

In some embodiments, the vehicle aspect is one or more of engine oil,engine light, oil pressure, battery status, electric powertrain status,phone lists, temperature, cooling system, charging system, radiosettings, geo-location data, advisor history, tire rotation, tire heath,oil filter, battery, brake pads, brake systems, wipers, coolant, brakeoil, transmission fluid, air filter, recall condition, broken part,service cycle, maintenance updates, part updates, advertisementsregarding the vehicle, suggestions, and combinations of two or morethereof.

In one embodiment, a method for assigning and using advisor accounts fora vehicle is provided. The method includes receiving a request, at aserver, to define an advisor account for a vehicle associated with auser account, the request identifying an advisor entity, a vehicleaspect to be assigned to the advisor entity, and privileges assigned tothe advisor entity for the vehicle aspect. The method further includesgenerating the advisor account, at a server, for the advisor entity as asub-account of the user account that is associated with the vehicle. Themethod also includes sending instruction data, from the server, to thevehicle, the instruction data defining that the vehicle aspect isassociated with the advisor account. The method also receives dataupdates, at the server, from the vehicle for the vehicle aspect, fromtime to time, the data updates being displayable on a user interfacethat is accessible to the advisor entity, the user interface beingrendered by the server that provides access to the advisor account,wherein the privileges define a level of access to data about thevehicle or remote access of the vehicle via the advisor account for thevehicle aspect and the user account is enabled to create a plurality ofadvisor accounts, each advisor account is associated with the vehicleand assigned to different advisor entities for different vehicleaspects, each of the different vehicle aspects being assigned with sameor different privileges as defined in the advisor account. The method isexecuted by a processor.

In some embodiments, a vehicle aspect is a part, feature, function,operation or combinations thereof of the vehicle, and each vehicleaspect or multiple vehicle aspects are assignable to the advisor accountwith associated privileges.

In some embodiments, the data updates define characteristics or changesin characteristics of the vehicle aspect.

In some embodiments, the advisor account enables remote access to thevehicle to act upon a feature of the vehicle aspect.

In some embodiments, the advisor account includes a communicationprotocol to enable a user of the advisor account to provide adviceregarding the vehicle aspect.

In some embodiments, the user of the advisor account, in accordance withthe privileges, is enabled to perform remote diagnostics to provideadditional advice, order parts and schedule appointments.

In some embodiments, the advisor accounts can be issued to any type ofvehicle. Without limitation, the types of vehicles can include personalvehicles; company owned vehicles, fleet vehicles, delivery vehicles,mass transport vehicles, shared vehicles, electric vehicles, two wheelvehicles, tractor trailers, commuter vehicles, trains, planes, cars,trucks, campers, trailers, etc.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows example profiles settings for a vehicle, and association toroles, in accordance with one embodiment.

FIG. 2 shows additional role settings for different users, in accordancewith one embodiment.

FIGS. 3-5 show additional vehicle profile settings, in accordance withone embodiment.

FIGS. 6-9B show example pairing of a vehicle to a user profile, andexamples of a shared vehicle transfers of profiles for limited use ofthe profiles on the shared vehicles, in accordance with one embodiment.

FIG. 10 illustrates validation method for enabling a profile on avehicle and biometric validation, in accordance with one embodiment.

FIG. 11 illustrates various settings for a profile and adjustments thatcan be made over the Internet via a device, e.g., using a portabledevice or the vehicle electronics and displays, and remote controls andsettings in accordance with one embodiment.

FIG. 12 describes a system in which a user interacts with a model viewcontroller software environment useful for processing APPS using APIs onvehicles with vehicle operating systems capable of processing computercode, in accordance with one embodiment.

FIG. 13A describes how vehicle on board computer with input outputsystem useful for accepting input, processing input and displayingresults in conjunction with stored computer readable programs orfunctions in the forms of APPs may be structured, in accordance with oneembodiment.

FIG. 13B describes one example of how stored data and functiondeclarations may be compiled to provide intermediary access to avehicle's computer controlling vehicle systems, in accordance with oneembodiment.

FIG. 13C describes a set of computer readable and executable code thatcan be compiled together by a third party APP developer in the form ofan APP, in accordance with one embodiment.

FIG. 14 describes the stepped flow of events as a user interacts with anAPP, in this case, an HVAC APP, in accordance with one embodiment.

FIG. 15 Describes further ways an APP may take, process and produceresults, in accordance with one embodiment.

FIG. 16A describes an ecosystem where an APP in conjunction with avehicle API may work together to make assumptions, make decisions andtake actions, in accordance with one embodiment.

FIG. 16B describes how one of many types of inputs into an assumptionand reasoning logic module can be compiled over time, in accordance withone embodiment.

FIG. 16C describes one example of what an assumption and reasoning logicmodule may produce using the data points collected on an ongoing basisin FIG. 16B, in accordance with one embodiment.

FIG. 16D describes an example list of decision the decision and actionengine may take based on information provided by the assumption andreasoning logic module and sets of assumptions created, in accordancewith one embodiment.

FIGS. 17-25 define methods and systems for assigning advisor accountsfor accessing data regarding the vehicle.

FIGS. 26-35 illustrate methods and systems for assigning e-keys forenabling access of a vehicle to a remote user.

DETAILED EMBODIMENTS

Embodiments of the present invention define methods, systems andapparatus for use in vehicles. The methods, systems and apparatusinclude electronics of vehicles that drive display devices in vehiclesand communicate wirelessly with Internet services.

The Internet services provide access to cloud services. The cloudservices provide access to user accounts and access to settings,configurations, applications and other customization defined by theuser. Customization can include user interface customization of avehicle display or displays. The customization can include the abilityto select specific applications (APPS) to be activated by the vehicleand interfaced via the display or displays, voice input, touch input,etc. The customization is also provided with a learning engine thatlearns use behavior by the user or patterns of behavior of multipleusers, and automatically implements settings or programming to aspectsof the user interface, or provides recommendations or notifications withrecommendations. The programming can include automatic programming atcertain times, days, months, years, etc., and can be updated or moldedover time as the user continues to use the vehicle UI.

In one embodiment, a user can assign and add advisor account to anyindividual. The Advisor account can be for any duration, and theduration can be set by the user. In one embodiment, the advisor accountcan be assigned to a guest driver of a vehicle. The guest driver can be,for example, a friend, a known individual, a service person, a valetperson or valet service, etc. The creation of an advisor account cantherefore be for a short duration, or long duration, or permanently, oruntil the account is canceled, stopped, revoked, expires, or eliminatedby the person/user that issued or created the advisor account. In oneembodiment, the advisor account can act to provide access to a vehicle.

In one embodiment, access can be by way of electronic keys (e.g.,e-keys), which can be sent by a vehicle owner/admin to some person orentity. For example, the user-owner of the vehicle can assign a valetwith access to the vehicle by going on an application (App or website)on a computing device (e.g., mobile or non-mobile device), identifyingthe recipient, identifying a mode for communicating with the recipient(e.g., text, email, message, notification, etc.), selecting the accountprivileges (e.g., what type of access, speed limits, geographicrestrictions, amount of time the e-keys will be valid (or else expire)),and requesting that e-keys be sent to the recipient.

In one embodiment, a user can access cloud services for a vehiclemanufacturer and identify the particular vehicle from selected choices.The user can then identify a customization profile for the vehicle bydefining the look and feel of a UI display, arrangement of vehiclecontrols on displays, add and associate third party APPS to the vehicledisplay, and save the configuration.

The configuration, in one embodiment, is saved to the profile of theuser. In one embodiment, the profile is saved on a database of aspecific vehicle manufacturer that offers the customization option. Instill other embodiments, once a configuration is saved to the profileaccount of a user, that configuration can be shared to other vehicles ofthe user. In still other embodiments, when a user buys a new car, thecustom configuration can be transferred either entirely or partially tothe new vehicle. In some embodiments, if the vehicle has more or lesssystem functions, the customization can be adjusted automatically or theuser can be provided with options to update the customization to add ordelete features. In one embodiment, the customization will befacilitated via a website. In one embodiment, the website may be of thevehicle manufacturer. In one embodiment, the website of the vehiclemanufacturer can allow the user to add APPS that are created by thirdparties. The third parties can create APPS that communicate with APIs ofthe system components of specific vehicles of the manufacturer. OnceAPPS are selected, the user can add them to the custom user interface(UI) display.

The user can also be allowed to arrange the APPS or icons of APPS in aspecific custom arrangement that is saved to the user's profile. In oneembodiment, the user's profile can also be run on various vehicles,other than those owned by the user. For instance, if the user is rentinga vehicle and the vehicle has access to cloud services, the user canenter his user name and password (or other identifiers), which log theuser into the cloud services and saved profiles. The saved profiles willthen enable logic to build a custom UI for the user based on the vehiclebeing driven. In one embodiment, the system components and APIs of thesystem components of the rented vehicle can be paired or linked to theuser's saved APP selections.

The user's saved UI configuration may also be transferred to the displayof the rented (or other vehicle) vehicle. A best-fit configuration canalso be generated using the user's profile selections, so that theconfiguration provided for the other vehicle will closely resemble orappear as it does for the configured vehicle. In other embodiments, theuser's use metrics can be monitored. The use metrics can include use ofAPPS, use be of system components of the vehicle, use of the vehicle,environment conditions, and historical actions taken by the user via theinput/output controls of the vehicle (e.g., buttons, levers, keys, fobs,display selections, display interface actions, communication actions,etc.).

These historical actions can then be used to define learned actions. Thelearned actions can be analyzed to change configuration settings in theuser's saved profile. For instance, if the user uses a particular APPevery day at a particular time, that APP icon can be surfaced to thedisplay or preset to start. The APP can then provide information to theuser at about the same time the user normally needs the information.Other historical use patterns can be monitored and such data can besaved to the user's profile.

The data can then be used by algorithms that build assumptions based onhistorical inputs by a user as well as environmental inputs, locationinputs, vehicle diagnostic inputs; internet connected marketing deals,the user's calendar, traffic conditions as well as news. The assumptionsthe algorithm builds are then processed into decisions and actions by anadditional algorithmic process to activate local or remote audio andvisual alerts, change vehicle systems, display information on avehicle's displays and request a decision from a user locally orremotely to complete an action.

A number of embodiments are described below, with reference to specificimplementations that refer to vehicles, but such implementations shouldbe broadly construed to include any type of vehicle, structure orobject. Without limitation, vehicles can include any type of movingobject that can be steered, and can include vehicles that are for humanoccupancy or not. Vehicles can include those that are privately owned,owned by corporations, commercially operated vehicles, such as buses,automobiles, trucks, cars, buses, trains, trolleys, etc. Examplevehicles can include those that are combustion engine based, electricengine (EV) based, hybrids, or other types of energy source vehicles.

A cloud processing system, as described herein, will include systemsthat are operated and connected to the Internet or to each other usinglocal networking communication protocols. A cloud processing system canbe defined as an interconnected and distributed physical or virtualsoftware defined network that utilizes virtual or physical processingand storage machines that enable various applications and operatingsystems to facilitate the communication with and between various clientdevices (vehicles, user devices, structures, objects etc.).

The communication with and between the various client devices willenable the cloud processing system to deliver additional processinginformation, data, and real-time metrics concerning data obtained fromother processing systems as well as client feedback data. Thedistributed nature of the cloud processing system will enable users ofvarious vehicles, structures and objects to access the Internet, and bepresented with more flexible processing power that will provide therequested services in a more effective manner.

The processing systems can be defined from various data centers thatinclude multiple computing systems that provide the processing power toexecute one or more computer readable programs. The processing of thecomputer readable programs can produce operations that can respond torequests made by other processing systems that may be local to avehicle's electronic system. For example, a vehicle can includeelectronics that utilize memory and a processor to execute programinstructions to provide services.

In other embodiments, the electronics of a vehicle can synchronize witha user's portable electronics. The user's electronics can include, forexample mobile devices that include smartphones, tablet computers,laptop computers, general-purpose computers, special purpose computers,etc. The various computing devices of the vehicle, and or the computingdevices of the user (smart devices) can be connected to the Internet orto each other. Provided that a user has access or account access to thecloud service, the cloud processing services on the Internet can provideadditional processing information to the electronics of the vehicle.

The wireless communication can include cellular tower communication thatcouples and communicates through various networks to the Internet, toprovide access to cloud processing 120. Other methods can includeproviding Wi-Fi communication to local Wi-Fi transmitters and receivers,which communicate with cloud processing 120. Other types ofcommunication can include radio frequency communication, such as802.11.ac, 802.11ad and subsequent wireless networking protocols,Bluetooth communication or combinations of Wi-Fi and Bluetooth. Itshould be understood that vehicle electronics can communicate with cloudprocessing 120 via any number of communication methods, so long asexchanges of data can be made with cloud processing 120 from time totime.

The communication can be made by vehicle electronics while the vehicleis on or when the vehicle is off, so long as communication andprocessing circuitry of vehicle electronics has a power source. Thepower source can include battery power that powers vehicle electronicsto communicate with cloud processing 120 when vehicle is turned off.When vehicle is turned on, the battery that drives vehicle electronicscan be recharged.

Still further, certain applications can increase in size when being usedor decrease in size to enable selection at a later time. For example,selecting the temperature system component may expand the systemcomponent to a larger space, thus temporarily removing other displayedcomponents. The user can also select other buttons to access othersystem controls, other apps, or modify or add applications or systemcontrols. When modifications are made, the modifications are saved to auser database and profile of the user, as managed by cloud services.

Cloud services will therefore allow any future modifications to be madeto the custom configuration at any time and from any computer connectedto the Internet. Still further, the custom configuration can betransferred to a second vehicle. If the custom configuration istransferred to a second vehicle, the system can select the systemcomponents for the second vehicle and attempted do a best match ofapplications available for the second vehicle that resemble or match theones used in a first vehicle. Specific settings, arrangements and otherfeatures may also be transferred to a second vehicle, by simplytransferring the custom configuration to a second vehicle.

In one embodiment, the functions of the specific applicationsillustrated in the display will be monitored and restricted depending onsafety considerations while driving. For example, if the interfacingfunctionality requires more interactivity with the display, or requiresa reading of text or inputting text, those functions will be disabledduring operation of the vehicle. Once the vehicle comes to a stop, or isplaced in Park, certain of these functions will be activated. In otherembodiments, other safety considerations will allow for applications toshift from outputting text to outputting audio or voice. The input canalso be changed from touchscreen, button touches, selections, and/orvoice input. In still other embodiments, safety considerations can allowcertain user interface components to move about the display to provideeasier reading while driving or automatic conversion of text to audio.

For example, content being displayed in the center panel display of thevehicle, can be automatically shown in the dashboard display region ofthe vehicle, such as in front of the steering wheel. In still otherembodiments, some content or display data can be moved from the centerconsole or the display in front of the steering wheel to the windshieldof the vehicle in a heads-up display area. Accordingly, algorithmsexecuted by the applications and applications of the manufacturer, cancooperate to provide functionality to the application features andinterfaces, while maintaining safety parameters defined by rules. Thesafety parameters will therefore allow content of the user interface tobe shifted around to various displays of the vehicle, or translated tovoice or audio at certain points in time.

These settings and customizations can be made through the web/cloudservices and tools provided by the website of, for example themanufacturer of the vehicle. In one embodiment, the cloud servicesprovided by the manufacturer can be provided by a partner of themanufacturer. The partners of the manufacturer can include softwarecompanies that develop, host, or manage certain functionality providedby the vehicle manufacturer. In other embodiments, the partner softwarecompanies can integrate tools or components with tools and components ofthe vehicle manufacturer. This provides for integration with one or morecloud services, software services, Internet services, and servicesprovided by systems of vehicles or systems of the vehicle manufacture.In either case, whether the software and logic is designed andconstructed by one or more entities, the cloud services provided by thevehicle manufacturer or the website that provides the tools forcustomization will appear as a unified simple to use interface for theuser. As mentioned above, the cloud services can provide databases forsaving the user profile and data associated with the user account.

The user profile can include settings made by the user, customizationsmade by the user, identification of applications purchased or added tothe vehicle customizations, etc. Still further, the user profile datacan be part or be associated with the user account. In this manner, theuser that customized a user interface can access the Internet at anytime, whether through the vehicle or through any other computing devicehaving access to the Internet and make changes, modifications, or accesscontrol features of the vehicle remotely. In one embodiment, the profileof the user can be accessed from any vehicle, such as rented vehicles orshared vehicles. Settings and profile data can then be shared for aperiod of time on any vehicle and use data on that vehicle can bestored.

When the user is not using the vehicle, the custom configuration can beturned off or locked out for another session. Once the user wants tostart a new session, the user can log back in and the customconfiguration returns. In other embodiments, the custom configurationwill automatically turn off when the user is not driving the vehicle orhas not logged into the vehicle. In other embodiments, the customconfiguration can be automatically turned on when the user is detected.The user can be detected using biometrics, login credentials, imagedetection of the face, fingerprint detection, retina scans, etc. In someembodiments, biometrics can include data used to identify the user, suchas face recognition, fingerprint reading, retina scans, voice detection,or combinations thereof. Still further, the custom configuration can betransferred to other vehicles.

If the user wishes to use his or her custom configuration in anothervehicle, the user can login to the custom configuration or user accountfrom another vehicle. If the other vehicle does not have all the systemcomponents needed to define the custom configuration, the customconfiguration can be supplemented with other similar componentsautomatically. In other embodiments, the custom configuration can betransferred from one vehicle to another, or when the user buys a newvehicle. In another embodiment, the custom configuration can be adjustedbased on the driver. The custom configuration can also be presetremotely from the Internet, using the cloud services. The customconfiguration can also be configured to provide limited use of certainsystems or the vehicle, such as when a guest is driving the vehicle. Inother embodiments, restrictions can be placed on the vehicle speed,location of driving, and automatic notifications for the user or themaster user of the vehicle. The master user of the vehicle can have amaster account with administrator credentials.

In still another embodiment, the vehicle can be loaned to a child ofdriving age (under 21/18 years of age), and the child can be providedwith restricted use of the vehicle. When the child exceeds or does notfollow the restrictions of the vehicle, automatic notifications can beprovided to the user that is the administrator of the vehicle. Thenotifications can be by cell phone, smartphone, tablet computer, mobiledevice, text messages, phone calls, commendations of phone calls andtext, audio messages, audible sounds, vibrations, and commendationsthereof. History use of the vehicle can also be maintained in cloudservices. The history use can provide the user with information as towhere the vehicle has been, the speed or events, violations thatoccurred when use of the vehicle etc. The configuration can also providemessages to the driver warning the driver of when the vehicle hasexceeded a restriction, or is approaching a restriction in use, drivingarea, speed, etc.

The screen displays can have various configurations, placements, sizes,number of pages, tabs, etc., and the user can provide controls for someor all of the interfaces and controls in certain locations. Theselection can be enabled for third-party applications. The third-partyapplications can be selected from the vehicle site, or by providinglinks to third-party sites. The third-party applications can bepre-identified by the site and displayed to the user if they arecompatible with the particular vehicle selected. In another embodiment,the third-party applications can all be shown to the user whether or notthey are compatible with the vehicle. Upon binding/pairing or attemptingto find application for the vehicle, compliance as to whether theapplications operate or comply with the particular vehicle can be made.

In one embodiment, certain third-party applications can be reviewed bythe vehicle site administrators before they are made available to usersfor selection. In other embodiments, the third-party applications can beapproved or disapproved. In still other embodiments, the third-partyapplications can be augmented with restrictions made by the vehiclemanufacturer, or dictated by law. The restrictions can be applied, basedon the anticipated interfacing with the vehicle interfaces, to ensuresafety during driving. For instance, if a particular applicationrequires entry of text, navigation of controls, or other activities thatwould distract the driver during operation of the vehicle, such vehiclecontrols or application controls for application interfaces can betemporarily disabled, or can be automatically transferred to a heads updisplay, or can switch to take audio vocal input from the user. In someembodiments, when the vehicle has come to a stop or is place to park,certain controls or interfaces can be re-enabled, or moved back tooriginal display location or converted back from voice input to touchinput. In one embodiment, tools provided by the vehicle site orthird-party site can provide for customization of the layout of thedisplay screens of the user interface.

The customization can include organizing or laying out system interfacesas well as application interfaces, such as those interfaces provided by3rd parties. In one embodiment, interface rules are applied to determineif the system interfaces can be replaced with third-party applicationinterfaces, while providing access to the control interfaces via theAPIs of the systems. For example, if the user wants to provide a customspeed indicator, the speed indicator must be compliant (via APIs and/ormapping) with the system interfaces so that the speed readings can bepopulated to the third-party application. In one embodiment, rules canbe integrated with or applied to the applications and system userinterfaces for when the vehicle is moving. As mentioned above, suchrules can limit interactivity with certain user interfaces while thevehicle is moving to prevent unsafe driving. In one embodiment, thecustom user interface is saved to the user profile.

The user profile may contain settings, such as selections of the userinterface components associated with the system of the vehicle, as wellas user interface is provided by third-party applications. In addition,the user profile can contain and store settings provided by the user.The settings provided by the user, as mentioned is this disclosure canalso be learned settings based on use. The settings can further includeremote access settings, as well as settings allow the user to controlvehicle components from a remote location or a remote computer. Thesetting can also include providing access to the user account to viewhistorical driving patterns, recent driving activities, the performanceof the vehicle during specific driving sessions, the performance ofspecific vehicle components, etc.

In one embodiment, the custom user interface configuration can betransferred to the vehicle. The custom configuration, as mentioned aboveis stored in the database of the vehicle manufacturer, or a databaseheld by a 3rd party that cooperates with the vehicle manufacturer toprovide cloud services. The database, in one embodiment, is a networkaccessible storage which allows access to the user to program and modifythe user interface using any computer or device having access to theInternet, including the vehicle itself or a third-party vehicle. Themethod then proceeds to operation where the custom user interface can beactivated in managed for Internet connectivity for components of thecustom interface. For example, the vehicle's Internet access protocolscan be set, or registered with an Internet provider or service providerfor the cloud services. The service provider for the cloud services canbe the vehicle manufacturer, a company cooperating with the vehiclemanufacturer, a third-party company, or combinations thereof.

In one embodiment, the method/logic can also enable local communicationwith mobile devices that may be in the vehicle. The enablement may beprovided by allowing synchronization with the computing system of thevehicle, or with the computing communications of the portable device.For example, the local communication can be paired automatically, basedon a preset pairing process where pairing keys are entered. Thisprovides for automatic settings and synchronization when the user entersthe vehicle with the portal device. As mentioned above, user interfacesassociated with applications loaded on the user's portal device can alsosynchronize to the display screens of the vehicle, as predefined by theuser.

In one embodiment, vehicle settings are saved to either a memory numberbutton on the vehicle or synced to a key fob, or accessible via aninterface or voice activation. In one example, a vehicle operatorprofile is provided to allow users to maintain their individualizedprofiles, settings and accounts for vehicles from any internet connecteddevice or be able to login to their vehicle physically in or near thevehicle by the use of a fob, thumb print, eye scan and or manual loginusing an input device that interacts with the vehicle's login system.

In one embodiment, the profile can be managed at a user account saved toa central or cloud distributed system, to manage access. Any vehicle canbe abstracted so that any user can log into any vehicle if they have anaccount that allows access to that vehicle. For instance, a vehicleowner with the role of “administrator” (e.g., an administrator of a useraccount that has a profile associated therewith or multiple/subprofiles) can create logins for his or her vehicle(s) for additionalusers such as his or her children, spouse, mechanic, and valet driveramong other applications. Logins can be created for individuals or forroles such as the role of “child” where all users with the role “child”would have the same vehicle specifications applied to the vehicle theywill be logging into. Similarly, the role of valet can be given andshared by any valet driver.

The purpose of abstracting vehicle operators from the vehicle itself isa shift from the current state of the art in which settings are vehiclespecific—each vehicle typically only having the ability to store 1-3sets of settings, to where vehicle settings are user specific and 1−nlogins can be managed through an access management system. Theembodiments defined herein allow each user to apply his or her settingsto any vehicle based on their login information in which they providetheir login and password. When a user logs into a vehicle, the vehiclewill determine locally on board and/or communicate remotely with acentral or distributed access management system to determine thevalidity of the login presented to the system. If the user's login isrecognized, the system will apply settings and use privileges to thevehicle prescribed by the login.

Logins can have “role” specific settings and privileges or settings andprivileges set only by the administrator that cannot be overridden bythe user of the login. For instance, an administrator may create a loginfor “John” their 16-year-old son. The administrator can apply settingsto John's login that John cannot override such as the maximum speed thevehicle can travel. For instance, Although the vehicle may have theability to travel at a speed of 130 mph, John's login will only allowthe vehicle to travel at a speed up to 90 mph. Additionally, every loginmay have settings that the user of the login can toggle to their likingsuch as the list of radio stations they would like pre-programed everytime they log in to any vehicle that accepts their login.

Logins can control all aspects of a vehicle's behavior and can beattributed to individuals or roles. These settings can be toggled via anetwork connected device such as a computer, web application,smart-phone or directly on the vehicle. Administrators can decide whichsettings are locked for specific logins or roles, which are open for thelogin user to toggle and which settings are to be enforced depending onthe time of year, or time or day etc., or when a condition or event isdetected.

Login settings that can be set and remotely administered include but arenot limited to, driving characteristics (rate of speed, fuel consumptionguidelines) location based settings (GPS aided travel restrictions,travel radius boundaries, dynamically loading maps, dynamically loadingdirections, dynamically loading fuel, charge and battery service andpurchase locations etc.), time of day based use restrictions (daydriving only for example), automatic purchase settings (financialinstitution linking for automatic purchasing of fuel, charge time,batteries, car washes, etc.), fuel settings (Electric only, fuel only,hybrid only etc.), refueling routing and purchase (incentive basedre-fueling maps, incentive based refueling offers etc.) drivingcharacteristic settings (sport, comfortable, soft, off-road, highperformance, economy mode), entertainment system settings (radio memorysettings, internet access or restriction, streaming services settings),comfort & HVAC settings (climate control, seat positions, seatheater/cooler, suspension/ride settings, entry lighting, remote start,remote stop etc.) tracking/metric settings (camera/video recordingguidelines, mileage, top speed, average speed, MPG, wear and tearsettings and notifications, historical travel maps).

Automatic purchase settings can be processed in response to requestsfrom the vehicle. The request can be, for example, to transact a paymentis for one of a car wash service, a fast food service, a toll roadservice, a goods purchase service, a rental service, a lease service, orcombinations thereof.

Additionally, combinations of settings or setting profiles (such as“sport” where your seat moves to sport position for additional support,suspension stiffens, throttle response becomes aggressive etc.) can beset as well instead of individually setting use characteristics. In oneembodiment, logins are user specific, not vehicle specific, so anyfamily member can use their login on any family vehicle and the vehiclewill perform based on the metrics and restrictions dictated by the loginused to operate the vehicle.

Companies or entities can create and manage logins to company vehiclesfor delivery drivers, car washers, and mechanics among otherapplications. Each login can be configured to provide or restrict accessbased on the user logged into the vehicle. A company may only allow adelivery vehicle to travel at a maximum speed of 80 mph to limitreckless driving. A company may create a role of “local delivery only”where a driver with that login can only drive the vehicle within theirterritory. Breaches in territory travel will result in a recorded eventand notification to the vehicle administrator as well as the vehicleoperator. A grace period will be given to re-route back into thedriver's territory before more aggressive vehicle disabling mechanismsare deployed. The driver will be given visual and audio cues as to howto avoid vehicle disabling.

A dealership can grant “test drive” logins to potential customers, whichallows them to operate less than 100 mph and only within a 5-mileradius. In one embodiment, alerts or notifications can be automaticallytriggered if violations in the restrictions are detected. A dealershipmay also grant a “demo” login for instance which showcases the vehicle'scapabilities, available APPS, features and benefits. Variations of the“demo” login can be used on variations of potential buyers. A “18-24year old demo” may be useful for enticing that demographic and showcasesthe vehicle's features 18-24 year olds are most receptive to.

A valet can be given a password to login only as “Valet” which willimpose restrictions on trunk operation, vehicle speed operation, vehiclelocation notification settings etc. A recording option can be provided,which can set a recording within and around the vehicle when in thevalet mode. This way, the user can login to see what the valet driverdid while in possession the car, in case the owner feels that somethingis not correct when the vehicle is returned to the owner. Additionally,while the valet is driving the car, a notification can be provided tothe valet that will alert the valet that recording is in progress, andtheir face can be shown on the display while the valet parks the car.

A user may set the valet login to alert the user that left the vehiclewith a valet that the car has traveled beyond the allowed radius or hasreached a speed greater than 100 mph, for example. This alert can besent wirelessly to an email address, texted via mobile phone number orsent to a mobile device having a login-profile mobile applicationcapable of sharing current vehicle location, speed, fuel status amongother metrics. The last logged in user of the vehicle or vehicleadministrator can send visual, audio or auto override notifications tothe valet letting them know they need their car back, they are travelingtoo fast or even auto shut down to prevent theft.

A parent can set up a login to the family vehicle for their child thatonly allows the child to drive within a certain radius. For example thevehicle may only be used to drive between home and school. A map can beoutlined on the account management interface by a parent when setting upthe child's login to support the home to school restriction intended.

In one embodiment, a parent or company may give a child or companydriver a login that also carries a financial allowance connected to oneor more financial institutions administered through the accessmanagement and/or login management system by administrators. Forinstance, a child may have the need to re-fuel the vehicle by purchasingeither traditional fuel, battery units, and or charging time but aparent does not want to give a general credit card to the child. Theparent will set a budget for fuel purchase for the given login and thelogin will then allow the vehicle will communicate with the fuel,battery, and or charge-dispensing unit automatically using a wired orwireless communication systems funding the purchase automatically up tothe allotted budget set in the login of the vehicle.

In one embodiment, these features are useful for fleet vehicles wherecompany vehicle users currently use a corporate credit card to purchasefuel where fraud may exist in the form of using company credit cards, orcompany fuel accounts to fuel personal vehicles. The new system ensuresonly the company owned vehicle is approved to purchase the traditionalfuel, battery, charging time and also maintains metrics on which loggedin user consumed fuel and re-fueled which vehicle.

In one embodiment, a process is created so that some or allmanufacturers use the same type of login/access management system. Byway of example, any user can log into any vehicle from any brand in sofar as they have account creation access or a recognized login. Oncelogged in, each vehicle will receive and impose the login-based settingsas long as the manufacturer supports the login/access system.

FIG. 1 shows various methods a user can interact with a vehicle loginsystem, in accordance with one embodiment. The user may use anynetwork-connected device ranging from a mobile computer, mobile phone,mobile network device all connecting to a remote converged ordistributed network cloud system. The user may also interact with thevehicle login system directly on or near the vehicle. The user supplieslogin credentials to a vehicle login interface which are sent to theremote distributed or centralized user login authentication system oronboard vehicle authentication system. The processing logic receivingthe login credentials processes the data and returns an authenticationresponse to the user attempting to log in. If the authentication is asuccess, the vehicle the user attempted to log into has vehicle settingsapplied to it and the user is allowed to operate the vehicle. If theauthentication is a failure, the user is presented with a failed accessnotification on the login interface.

FIG. 2 shows two different types of users and an example of how the useris organized, in accordance with one embodiment. In this example, User 1is an administrator of a vehicle login system over vehicles he or sheowns. User 1 has the ability to add or remove logins, roles and vehiclesto his login system. Since User 1 is an administrator, he or she can addmore logins and or roles to the system to allow a family member to haveaccess to the family vehicles for instance. In this case, a familymember “User 2” is shown. The administrator has given this family membera login named User 2 and has granted two roles to User 2. User 1 mayonly want User 2 to have access to a certain vehicle and to certainroles only. User 1 may only want User 2 to have access to the vehiclefor the purposes of traveling between school and home. In this case User1 has created a role that is applied to User 2, which only allows thevehicle to travel within certain restrictions and geographicallocations.

In this example, User 2 does not have the ability to alter his or herlogin, role or vehicle since they do not have administrator access.However, User 1 can make changes on behalf of User 2. The full range ofsettings over a vehicle that applies to a given role or login is a superset of settings. User 2 may have access to a subset of settings thatUser 1 allows changes to by User 2.

FIG. 3 shows a graphical representation of a example set of settings anadministrator such as User 1 may have to administer logins, roles, andvehicles. FIG. 3 further expands the depth of settings, including butnot limited to, vehicle administration, adding or deleting users androles, vehicle global settings that apply to all roles and logins,adding or deleting vehicles among other settings.

FIG. 4 shows one sample of many potential configuration settings for agiven vehicle. In this case, User 2 has a login created for him or hernamed “CHILD”. This login contains a set of settings that may or may notbe configurable by User 2 since User 2 is not an administrator, only asubset of settings are open to him or her to alter. The drawingillustrates the settings that are user editable and admin only orrestricted. The left column lists the type of settings corresponding onthe same row on the right column. These settings are examples and may bealtered, added to, or subtracted from in different embodiments. Forinstance, fuel use settings allow an admin in this case to choose whattype of fuel the user login CHILD is allowed to use while logged intothe vehicle. Similarly, location based settings allows an administratorto draw out a map of the area the user login CHILD is allowed to travelwithin while logged into the vehicle.

FIG. 5 describes extended settings from FIG. 4. This figure describesadditional vehicle settings that are configurable by the user with thelogin “CHILD” and those that are only configurable by User one being theAdministrator. FIG. 5 also describes a subset of settings a user loginCHILD in this case is allowed to change. For example, the user loginCHILD is allowed to select his or her radio stations, streamingservices, and Internet access settings for a unified experience in anyvehicle they log into using this log in. Similarly, the user login CHILDcan access driving modes and set the vehicle mode to sport for instance.It should be understood that the example “CHILD” profile is just that,an example, and any type of user profile may be set with the definedprivileges and/or restrictions.

FIG. 6 illustrates an example of utilizing a profile of the user, toaccess cloud services 120, and a database 115, in accordance with oneembodiment of the present invention. In this example, a user may utilizea connected device 110 to access cloud services 120. Using the connecteddevice 110, the user, in this case Bob, is accessing his universalprofile settings. His profile settings may include settings that havebeen selected before in earlier sessions, or default settingsimplemented by a vehicle manufacturer, or another user such as anadministrator. In the example, the user may access particular activesettings managed by cloud services 120 which can cause Bob's profile indatabase 115 to be updated.

In one embodiment, Bob's profile can include specific settings,preferences, use history, and learned settings from earlier uses of oneor more vehicles. The profile settings defined by Bob, are thentransferred by cloud services 122 one or more vehicles utilized by Bob.For example, if the user wishes to utilize his regular everyday car, theprofile settings may already be stored on the vehicle. If the userwishes to utilize a different vehicle, such as a friend's vehicle, arented vehicle, a shared vehicle, a temporary vehicle, a loaner vehicle,a test drive vehicle, a company vehicle, etc., the user's profiles canalso be transferred to that vehicle.

The user profiles can include standard settings that may be set at thevarious vehicles, or custom settings that can be selected for the userbased on learned settings over time by use of various vehicles. In oneembodiment, the user profiles are continuously updated and store to adatabase 115, which is accessible by cloud services 120. Database 115may include data storage, such as cloud storage, data center databases,distributed databases, local storage on vehicles, network storage, andthe like.

FIG. 7 illustrates an example of a user (Bob) that may wish to utilize acar 200, in accordance with one embodiment of the present invention. Forexample, the car 200 may be a shared vehicle, such as those commonlyshared in urban cities. Shared vehicles are those that belong to acompany and where the company provides accounts to users to access thevehicles for specific trips, specific times, periods of time, etc. Usersthat share those vehicles typically park the vehicles at differentlocations throughout an urban city. Users wishing to find a vehicle touse can access an application or website having access to an Internetconnected application to find the vehicle closest to the particularuser.

Once the user has located a proximate vehicle, such as car 200, the usermay approach the vehicle so as to utilize the vehicle 200. In oneembodiment, when the user approaches the vehicle, and comes in closeproximity to the vehicle as detected by the geo-location of the usersmobile device, a pairing request can be detected. The pairing requestmay be triggered once the proximity zone of the car 200 and theproximity zone of the user substantially or partially overlap. Theproximity zone's may overlap when the user comes in close proximity tothe vehicle, such as within a few feet, within a mile, or the user hastouched or bumped the vehicle.

The pairing request may be automatically sent by the users device tocloud services 120. The pairing request can include sending the model ofthe vehicle 200 that may have been obtained by the users mobile devicefrom the vehicle 200 directly. In the illustrated example, the pairingrequest by the users mobile device can include identification of thevehicle that the user has come in close proximity to. A pairing module170, can then communicate with a mapping engine 118 that determinesinformation associated with car 200.

An automaker database 116 can include data regarding a plurality ofvehicles, including standard user interfaces, configuration interfaces,and other information necessary to provide user Bob with a custominterface for vehicle 200.

The mapping engine 118, in this example includes a map or thatcommunicates with the automakers database to identify the settings,applications, APIs, or modules that allow integration of Bob's userprofile from the user profiles database 160 so that Bob's profile can besent to car 200. In the illustrated example, the mapping engine, the ofthe mapper, will obtain Bob's profile 160 for cloud services and obtainvehicle information for the user interfaces of the vehicle desired foruse by the user.

The mapping engine 118 will the transfer Bob's profile to vehicle 200.At this point, the user, Bob, can be provided with an interface on amobile device to allow access to the vehicle. The user interface caninclude a plurality of screens with instructions, check information,cost information, billing information, etc. As illustrated in FIG. 7,the users mobile device can provide various notifications, such asidentifying to the user that the user standing next to a blue model M7from maker C. The user interface can ask Bob if Bob wishes to pairsettings to the specific vehicle 200. If Bob desires to actually utilizethe shared vehicle 200, the pairing request may be initiated asmentioned above.

FIG. 8 illustrates another embodiment where the user Bob has utilizedhis mobile device 100 a to define or access a plurality of settings. Inone embodiment, the user may register 214 with a car sharing service,such as via a user interface or application having access to theInternet and the company providing the service. Cloud services 120 canthen provide access to the profile database 160 where Bob's profile maybe stored. The profile 160 may be accessible to 3rd parties, such as carsharing service.

Also shown in cloud services 120 is the car database 116/115. The cardatabase can then be provided with information from the car sharingcompany 210 that identifies the cars that the company owns and that areshared with the service. The car data including assigned IDs to thevehicles and cars can be stored in the car database 116/115. Additionaldata can be supplemented from vehicle manufacturers 212. The cloudservices 120, in accordance with one embodiment, can include logic forprofile identification for vehicles 224, logic for proximity detection222, user request logic 220, and other managing logic for receivingrequest from users, managing databases from a car sharing database,managing data from vehicle manufacturers, and receiving request tomanage profiles an axis vehicles.

As illustrated, when the user Bob approaches the vehicle 200, the Bob'smobile device 110 a can identify the closest car, which may be car A. Inthis example, Bob is identified to be proximate to the car having an ID1528ABC. In one embodiment, when the user comes in proximity to the car200, the car can beep or light up when enabled, it can open the doors toallow the user to access the vehicle when the logic has paired the userto the vehicle, the profile of the user can be transferred to thevehicle, the use of the vehicle is managed by the user's online account(storing historical use data and any billing information), automaticpayment for use can be made from predefined payment arrangements storedin the profile, and use of the vehicle can be restricted to predefinedrules, based on the profile. Accordingly, the profile database 160 caninclude both profiles of the user, such as user settings, as well asprofile restrictions that may be set by the car sharing service.

FIG. 9A shows one example process for utilizing user profile settingsfrom a registered user and utilizing settings of a shared vehiclenetwork, in accordance with one embodiment of the present invention. Inthis illustration, operation 300 receives the user profile settings froma registered user of a shared vehicle network. The registered usersprofile can be obtained from a cloud services profile, such as theprofile used for a number of vehicles which may be in or outside of theshared vehicle network.

In another embodiment, the profile may be the profile set by the sharedvehicle network, based on the service contract entered by the user. Inoperation 302, vehicle IDs for each vehicle assigned to a shared vehiclenetwork are received by cloud services 120. Cloud services 120 willtherefore maintain a user database 160 with a plurality of userprofiles.

Cloud services can also maintain a vehicle inventory database 310 forthe shared vehicle network. Servers 350, which operate cloud services120, and therefore managing access database 160 and 310, as well asprovide logic for providing access to vehicles, unlocking vehicles, andtransferring user profiles to specific vehicles. In operation 360, theservers 350 may receive a request to locate a vehicle on a map from acomputing device. The request may be provided with reference to theuser's current location, using GPS or the like. The request is thenprocessed by servers 350, and servers 350 communicate the forward a listof available vehicles proximate to the user or for the users identifiedarea in operation 362. In operation 364, a selection request is receivedfrom the user for a specific vehicle and a reservation is made for theuse of the vehicle for a set period of time.

In operation 366, a command is sent to the vehicle the signal alert whenthe user is detected to approach the vehicle within a particulardistance, notifying the user that the vehicle is the vehicle that theuser reserved. This provides for a method of allowing the user to easilyidentify the vehicle that the user reserved. For example, if the user isinstructed to go to a specific parking lot to identify the vehicle thatwas reserved, the user would have a difficult time identifying whichvehicle it is that the user reserved. However, by allowing cloudservices to signal to the vehicle to sound the alarm, turn on a light,beep, for make any other identifying gesture, the user can easilyidentify the vehicle in the parking lot.

In operation 368, a user interface is provided to the user's mobiledevice that will provide a notification to the user indicating that theperson/user has arrived at the vehicle. In operation 370, the usersprofile is transferred to the vehicle. The transfer of the profile willallow the settings of the user to automatically be set in the vehicle.The settings can include, for example, temperature, radio settings, seatsettings, meter settings, air settings, etc.

In operation 372, the settings that are made by the user when in thevehicle or adjustment settings can be sent back to the user profile.Thus, when the user offering the vehicle and making changes to his orher profile, those changes can also be communicated back to the profiledatabase in cloud services 120. This provides for a continuous feedbackloop over time, to allow the users profile settings to be managed andmaintained current to the users best liked preferences. The operationthen proceeds to B in FIG. 9B.

In operation 374, it is detected that the user has completed use of thevehicle upon some user entry at a computing device. The computing devicemay be computing device of the vehicle, or a mobile device. The entrycan be, for example, the user logging out of the vehicle indicating thatthe user has terminated use of the vehicle. At logout, the vehicle'soriginal profile settings will then be returned, and the users customprofile settings will be terminated.

In operation 378, a report sent back to the server regarding the use ofthe vehicle and the charges to the users account for the use. In oneembodiment, the use reporting can occur continuously while the user isdriving vehicle. In operation 380, the drivers session log can be saveduser profile, keeping a history of the user's travels. In operation 382,survey data can be requested of the user regarding the vehicle use.Because the user was utilizing a shared vehicle, feedback from the usercan be helpful to potential future users that may want to rent orutilize vehicles from the same company.

The user may be provided with options to publish likes and dislikes orcommentary to a social network 390. Ratings can also be transferred torating companies, such as those that allow internet users to view usercomments, reviews, complaints, etc. The social network 390 can allow thedata to be open data 394, or data that is shared with friends 392. Inoperation 384, problems with shared vehicle can be reported to thevehicle network to allow repairs before making the vehicle available forreuse. Cloud services for the shared vehicle network can then be updatedin cloud services 120. For example, if the vehicle has been identifiedas having some mechanical malfunction, the cloud services can updatethat vehicle as being out of service, so that discovery of that vehicledoes not cause users to access that specific vehicle that may be out ofcommission.

FIG. 10 illustrates a user (Bob) entering the vehicle, such as a sharedvehicle 200, in accordance with one embodiment of the present invention.In this example, the user has been identified by the vehicle, such asusing a camera 402. The camera 402 may use face detection 406 toautomatically identify the user, and set the users preferences andsettings for the vehicle automatically. In some embodiments, this allowsverification that the user driving the vehicle 200, from the sharednetwork, is the driver that unlocked the vehicle from a remote location(such as a mobile device). In this example, the vehicle 200 may alsoinclude a plurality of cameras, such as cameras 404, 408, 410, 412, 402,etc. Any one of these cameras can be accessed from a remote location, ifthe user's profile provides access, or the privacy setting allows suchaccess.

These cameras can be used to detect and monitor the exterior portions ofthe vehicle as the vehicle drives around, as well as interior portionsof the vehicle. These cameras can be used by the vehicle sharing companyto monitor the status of the vehicle, and the location where the vehicleis parked. In one embodiment, the user who has rented the vehicle canset a privacy setting to disable certain cameras. In one embodiment, aspeaker 420 can be activated to allow the vehicle to speak andcommunicate with the user. Vehicle electronics and logic 400 can be incommunication with cloud services 120.

Cloud services 120 can also be in communication with user profiles 160.In one embodiment, the user profiles 160 can also include specificprofiles for registered users. In one embodiment, the registered userscan include a family of users. A specific family can have a number ofdrivers or users that have been registered with a service. For example,the database can include users ABC123xi (such code is only an example,and any form of ID/code can be used), and the users can include aparticular family or group of people. The group of people can also be agroup associate with a company, a sharing service, a group establishedfor a particular event, or other types of groupings. The vehicles cantherefore be monitored for use by the specific users in a particularfamily or group. In one embodiment, the particular family and groups canbe associate with their own profile history settings, which include datafrom their previous uses.

In one embodiment, FIG. 10 illustrates a process utilize to communicatebetween vehicles, users, and cloud services. In operation 450, a vehiclewith communications is provided with cloud services. The cloud serviceswill be in account, software, or interface that allows communicationwith cloud services 120. In operation 452, the user in the vehicle maybe detected, and the face of the driver or other biometric data can beused to identify the specific user sitting in the car. The detection ofthe user can, in one embodiment be enabled or restricted based onprivacy settings desired by the user.

In operation 454, the user may be identified and the users profile canbe automatically retrieved from cloud services and the user profile 160.The preferences settings for the user can be identified from thedatabase in operation 456, and the settings can be applied in operation458. The settings can be applied to the vehicle for the identified user.When the user terminates use of the vehicle, the settings can't bedeactivated, or return to a neutral setting.

FIG. 11 illustrates an example of particular types of settings that canbe set, or recorded, or accessed, in accordance one embodiment of thepresent invention. In one example, cameras 480 can be provided asoptions for access by the user. The cameras can be accessed to viewhistorical uses by the user, or can be access to view current and livevideo of the vehicle. For example, if the user has rented a vehicle fora period of time, and parked it in a specific location, the user canmonitor the vehicle from a remote device connected to the Internet.

Record settings 482 can also be set by the user, the vehicle provider,or cloud services. A plurality of recording options and access can beset or adjusted by the user from a remote location. Remote access 484also provides the user with options to control specific features of thevehicle. The control the vehicle can be set for a period of time whenthe users profile is associated with the vehicle.

In a car sharing environment, the remote access of the vehicle can beenabled during the period of time when the user is assigned or the usersaccount is assigned to that vehicle. In examples where the user owns thevehicle or is more tightly connected to the vehicle, the remote accesscan be provided by entering axis control information, credentials,passwords, usernames, and biometric data or combinations of one or more.

In still other embodiments, user interfaces are provided to provisioncustomized data regarding available charge station locations. In oneembodiment, users having other devices, such as smartphones or portableelectronics can obtain data, which can be shared with other userinterfaces. The sharing can be by way of a sync operation, that can beautomatic when the user enters the vehicle or on demand by the user. Inother embodiments, the application or program running on the userportable electronic device can continue to execute the processing, whileallowing the display of the vehicle to show all activity on the display.For example, if the vehicle electronics are not capable for processingan application or access a cloud service, the portable device can act asthe agent for the vehicle electronics. In one embodiment, the displayand I/O of the EV simply acts as a passive interface, while theprocessing or accessing to cloud processing is done by the user'sportable electronics (e.g., smartphone or the like).

In some embodiments, the user's portable device is already programmedwith access codes, passwords, etc., so the user may wish to use theportable electronics instead of having to program the vehicle. This isimportant when users share a vehicle. If users share a vehicle, one usermay have the electronics programmed to their likes or dislikes. Byallowing programming, data settings, etc., to be shared or synced (e.g.,temporarily or not), users can more easily share vehicles, while keepingthe settings that the user is used to having.

In still another embodiment, allowing the user's smart phone or portableelectronics to sync with an EV, users of rental cars can more easilystep into cars with pre-programmed settings. Thus, users thattemporarily use vehicles need not worry about programming the car'ssettings upon entering the car, but simply sync with the vehicle toallow the vehicle to run display, IO and services based on the customsettings of the user's portable device.

This processing that allows users to sync a vehicle with a user's customsettings stored in the user's portable device can also have applicationto car sharing environments. In big cities, companies allow users tolocate vehicles in a proximity to their current location, and simplyenter the vehicle using their membership code. In addition to providingusers with access to the vehicle, the user/driver's settings can besynced to the vehicle. This can include settings of the seats, themirrors, the temperature, the radio stations, and the Internet apps todisplay on the car's display, etc. Custom information, such as prioruses of the car, cost for driving, etc., can be displayed on the car'sdisplay, via the sync data from the user's portable device. The syncdata can be obtained at any time, such as by using the user's portableInternet link, etc.

In one embodiment, a user's EV or non-EV vehicle can be in communicationwith cloud services, and the cloud services can be interfaced with datafrom various entities that provide power for the grid, provide chargingunits (CUs), provide discounts to charge at particular CUs, geo locationservices, mapping services, live traffic data, etc. The user of the EVcan communicate with the vehicles electronics via a display unit and itsassociated electronics, can provide input via touch or voice, canrequest data regarding routs to local charge stations, cost estimates atthe various charge locations, how crowded the charge stations are at thevarious locations, etc.

The cloud services 120 are also accessible via a computer that hasaccess to the Internet, a smart device (e.g., smart phone, tablet,etc.), etc. Thus, data can be acquired from various sources and data canbe consumed by various sources. The data that is acquired, shared oraccessed can be launched on the user's device and then transferred toshare in real-time with the display and/or electronics of the vehicle.Thus, a unified access display can be customized to the user, regardlessof the vehicle that the user chooses to drive. This is in contrast tocurrent models that customize settings for one vehicle owner or owners.

In one embodiment, the user's settings are seamlessly transferred to thevehicle the user chooses to drive. This is especially useful for caseswhere a user drives many cars, but wishes to keep his settings constant.Settings can include cloud services, or local settings such as seatpositions for the size of the user, mirror positions, radio stations,weather stations, history of routs taken, favorite locations to visit,etc. The application that allows syncing of a user's settings on aportable device to the vehicle electronics is especially useful for carsharing applications, which is common in large cities and may expand inthe future. As car sharing increases, it is most useful to allow a userto save his/her settings in their mobile device, instead of relying onthe fixed settings of the vehicle. In another embodiment, it is alsopossible for a user to type in their universal login code (e.g., username/password) into the car display, and all of the user's settings aretransferred to the vehicle while the user is driving the EV. Once theuser stops using the EV, the car can go back to the normal mode foranother user to login. The data regarding the user's settings would, inthis embodiment, be saved in the cloud.

In one embodiment, user interfaces of a mobile device can share datawith the vehicle's display and native apps. App unification allows EVsystem to display APPS on the user's smartphone device in an opt-in PAIRmode. In one embodiment, this allows one person to enter another's EV,share apps on the EV display while in the EV, and when the person leavesthe EV, the Apps de-pair. This auto-sync facilitates sharing of data andalso allows users to unify their settings across any number of vehiclesthe user may drive.

In one embodiment, the synchronization will enable users to universallytransfer settings from portable devices to electronics of a vehicle. Insome embodiments, the vehicle that the user wishes to drive is not hisvehicle. For instance, the vehicle may be a friend's vehicle, a rentedvehicle or a shared vehicle. If the user has programmed settings in hisor her device, the settings that are useful for the vehicle will betransferred to the vehicle. Settings can include travel speedrestrictions, car seat settings, mirror settings, remote access to homecontrols (e.g., lighting, garage doors, etc.), radio settings, satelliteradio settings, internet settings, etc. In some cases, only somesettings are directly transferrable. In other embodiments, a databasecan be accessed to find a translation metric. The translation metric caninclude mapping tables that allow for settings to be transferred betweenfunctions of one vehicle to other vehicles. In one embodiment, vehiclemakers can upload their translation metric for each model and themapping tables can be used to provide the sync operation.

FIG. 12 describes a system in which a user interacts with a model viewcontroller software environment 1800 useful for processing APPS usingAPIs 130 on vehicles with vehicle operating systems 129 capable ofprocessing computer code. The APPS can execute profile retrieval,updates, and sync operations. The model view controller paradigm 1800shows basic interaction, control, processing, and updating of datauseful for manipulating and viewing resulting actions by to vehiclerunning an APP in such a system. Such a system useful for running APPSon vehicle operating systems will accept inputs by a user 121, cloudservices 120 via data streams, vehicle systems feedback and data streams1812 used by a controller 1804 that may constantly poll electrical,capacitive and physical sensors, and input streams to detect ifinteractions 1808 such as network passive updates, network activeupdates, user touch, user speech, user input, user selection amongothers has been triggered.

Each input 1804 will then trigger manipulation of the system's model1802 portion of the APP software paradigm thus invoking stored routineswithin APPS 104 which then in turn interact with the vehicle's APIsystem 130 built upon the vehicle's operating system 129. Depending onthe app presented to the user 121, the input may trigger stored routinesor functions on APP software or operating system level restricted storedroutines or functions.

After the processing of stored procedure code is manipulated witharguments provided by the controller 1804 inputs, visual and or sensoryresults are presented to the user in the view 1806 portion of the modelview controller paradigm. These sensory outputs, data streams,electrical signals may all be translated as additional options, results,dynamic updating, audio or visual graphical user interface changes 1810on any of the user's connected display devices. The user will noticethese results visually or audibly but may also feel or detect changes inthe vehicle's mechanical systems. Updates from the model 1802 may alsobe used to toggle vehicle settings 1814 which in turn may invoke changesin the vehicle's physical, mechanical and electrical systems 128.

Finally, the system controller 1804 may receive additional updates fromthe vehicle systems affected or additional user 121, cloud services 120,vehicle systems feedback inputs 1812 to re-engage the user in a cyclicalfashion. If no inputs are sensed, the system's controller will continueto poll its electrical and data I/O systems for input on a continuousbasis.

The model view controller paradigm 1800 described is one example of thesoftware input output lifecycle that may be used to invoke, manipulate,process, update portions of computer readable code such as APPS 104using an intermediary API 130 to communicate with the vehicle'soperating system 130. However, APPS 104 may be run on physically wired,wirelessly connected or remote devices having processing abilities totranslate the computer readable code in APPS into actionable invocationson one or more vehicles in order to facilitate or utilize the vehicle'selectrical and mechanical systems in prescribed or customizablefashions.

FIG. 13A describes how vehicle on board computer with input out putsystem 1900 useful for accepting input, processing input and displayingresults in conjunction with stored computer readable programs orfunctions in the forms of APPs 104 may be structured. Although system1900 describes one way to provide vehicle on board computing power torun APPs 104, the arrangement of the vehicle computer 1906 may bealtered or arranged in differing fashions with differing connectionrouting in order to achieve the same. In this example, vehicle on boardcomputer 1906 may be comprised of components such as the networkinterface 1910, memory 1912, a central processing unit 1914, an inputoutput buffer useful for streaming data 1916, storage 1908 having theability to store computer data in long term or short term fashion usefulfor stored computer code procedures in the form of an operating system129, intermediary stored procedure code in the form of APIs 130, storedsubsets of computer code procedures APPs 104 interacting with API 130 asan intermediary to the operating system 129.

In this example, the vehicle computer 1906 has the ability to transmit,receive and process information using wired or wireless connections. Onesuch wireless connection is provided by a wireless data sending andreceiving antenna 1928 connected to a network interface 1910 useful forpairing with and communicating data with portable or stationary wirelessdevices which may or may not be part of a network 1902. Such wirelessdevices include but are not limited to wireless displays 210 b, portablesmart phones 210 a, portable computers, 210 c and even stationaryobjects, structures, buildings, toll bridges, other vehicles etc. Thevehicle's network interface 1910 through antenna 1928 may alsocommunicate with cloud services 120 to receive instructions from aremote location that invokes stored programs such as APPs 104 on thevehicle's computer.

The vehicle may also send and receive data wirelessly in order toestablish a connection with a peer-to-peer ad-hoc network. Invocationsmay result in output data streams interpreted by wireless devices 210 b,210 a, 210 c as well as wired devices such as wired displays 210 d orvehicle integrated display devices such as windshield heads up projecteddisplay or integrated glass displays 210 e. All data streams generatedby APPs 104 stored on the vehicle's computer may also be triggered bywired devices such as vehicle sensors 1918, vehicle electrical systems1920, vehicle electrical systems 1922, engine control systems 1924,vehicle diagnostics systems 1926, user input as well as environmentalinput.

A user and or vehicle may find system 1900 useful in one example, wherethe user drives the vehicle past an electronic toll bridge where a feeis required to pass the toll bridge. The vehicle's computer willcommunicate wirelessly as it passes the stationary structuretransmitting and receiving information with it as it drives by. Theuser's vehicle may have an APP 104 installed on the vehicle computer1906 that can process the input using the computer's wireless antenna1928, network interface 1910, input output system, 1916 automaticallyresponding to the toll bridge with payment information. Once the paymentis received and processed, the APP 104 receives information from thestationary wireless toll taking device which is then stored eitherlocally on the vehicle's storage 1908 or remotely using cloud services120. The results of the transaction are then sent via data stream fromthe compute code running on the APP 104 to a display device(s) where theuser can visually confirm that the toll was paid, accepted and show theuser's remaining balance all through the GUI displayed for APP 104.

FIG. 13B describes one example of how stored data and functiondeclarations may be compiled to provided intermediary access to avehicle's computer controlling vehicle systems 1950. Such routines, dataand functions may be arranged in such a way that limited access is givento third party code on APPs 104 to manipulate certain unrestrictedoperating system functions and vehicle systems. Such a method ofproviding the intermediary allowed stored function set to third partycode can be referred to as an API 130.

In this example of an API 130, computer readable code is arranged insuch a fashion that the type of API is described and in this case, anAPI that allows third party control of the vehicle's HAVC system isdeclared. A declaration may be useful for reserving the vehicle'scomputer long term and short-term memory in order to run storedprocedures. The shown declaration 1954 describes an example set of datathat may reference memory locations and their contents. The contents ofthese memory location may be modified by stored procedures 1956 orfunctions.

This HVAC API 130 has the ability to store data relating to thevehicle's temperature, status, target temperature, split zone temperate,data from electrical and mechanical sensors, calendar dates, errorinformation among others. Invocable functions 1956 are the methods bywhich a third party APP 104 may manipulate data 1954 on board acomputer. Free access is not given to the restricted data on a vehicle'scomputer, thus a structured method or methods are described for user bythird party APP developers.

These functions 1956 that may or may not take arguments in order toexecute may include functions in the example HVAC API that updatetemperatures for both the left and right or given zones of the vehicle,toggle are conditioning, allow visual skins on the APP GUI, manipulateschedules and displays etc. The HVAC API 130 described is one example ofhow one API can control one vehicle system. There may be variations ofthe APIs for multiple vehicle systems or one superset API that allowsaccess to all of the vehicle's systems through stored procedures ormethods.

FIG. 13C describes a set of computer readable and executable code 1970that can be compiled together by a third party APP 104 developer in theform of an APP. The APP 104 uses structured programming languages toexecute stored functions allowed by the vehicle's system API 130. Inthis example, the APP is a third party HVAC app that allows a GUI to bedisplayed to a user giving them the option to adjust the temperature onthe left or right side of the vehicle up or down. In this case, theAPP's GUI has provided a data stream to the APP letting it know that theuser has selected to set the temperature on the left side of the vehicleto 80 degrees and the right side of the vehicle to 76 degrees.

The APP 104 will then use functions available from the vehicle's API 130to manipulate the data on the vehicle's storage system which in turnwill be electrically polled by sensors, data streams etc. to manipulatethe vehicle's electrical and mechanical HVAC systems. The user willnotice the result visually by the data provided by the APP to the GUI aswell as environmentally as the temperature is changed in the vehicle.

FIG. 14 describes the stepped flow of events 2000 as a user interactswith an APP 104, in this case, an HVAC APP 104. The GUI shown for APP104 describes the first step 2002 where a user physically interacts witha sensor, screen, voice system etc. polling to see if an input has beenreceived. The user's input in 2002 has been interpreted by the app toraise the temperature on the left hand side of the vehicle to 80 degreesand maintain the temperature on the right hand side of the vehicle at 76degrees. This input invokes step 2004, which calls a stored function onthe APP 104 that is API 130 allowable with arguments. The storedfunction may invoke other helper or associate functions within the API130 in step 2006, which all in tern invokes restricted computer readablecode at the operating system and or kernel level in step 2008. Theseinvocations will then in turn command mechanical and or electricalsystems in step 2005 in order to achieve the requested response in step2002.

The results of the commands on the vehicles systems are based back tothe vehicle's operating system or kernel level in step 2012 which thenupdates data on the API 130 in step 2014 that the APP 104 is polling,such as updating the display to show the resulting temperature in step2016. The results of a function that is invoked at the API 130 levelupdating the display produces a data stream translatable and displayableby the vehicle's screen showing the APP 104's GUI in 2018.

FIG. 15 describes further example ways an APP 104 may take, process andproduce results 2100. FIG. 14 shows a way to interact with an APP 104locally but a vehicle computer system may relay data, inputs andinformation to the APP while connected to a wide area network, localarea network, cloud process 120 or private cloud. A remote action toinvoke change on an APP 1808 may be initiated via a network and pass tothe APP running on the vehicle 160 using the vehicle's antenna 1928 orwired interface. An APP 104 running virtually on a network or cloudservices 120 may also take input remotely and process the resultsaccordingly.

Some of the inputs and results 2102 that an APP can take and producelocally or remotely include but are note limited to the set 2104 thatcan receive an action, react to an action, control an action, manipulatedata models, report changes to a view or GUI, record events orincidents, learn the types of requests being submitted, learn the timesof request being submitted over time, learn the days of the year therequests are being submitted over time, generalize and interpretrequests, assume user intent in order to automatically invoke changes,automatically and pre-emptively act on behalf of a user, fine tunelearned user behavior etc.

The learned behavior (e.g., learned settings that provide for automaticprogramming) can be assigned to particular applications, particularsub-features of applications, to particular native system features ofthe vehicle, or combination of one or more thereof. The learned settingscan also be managed via an interface, which shows to the user settingsthat have been learned and provides the user with options to modifylearned settings.

The modifications of the learned settings can be made via the vehicledisplay or any other device having access to cloud services. The learnedsettings can also be communicated to the user via notifications. Suchas, “We noticed you like your truck temperature at 3 pm to be 60degrees? Please confirm,” or “We noticed you like your car temperatureat 8 am to be 75 degrees, this will be preset for you automatically,” or“We have detected your favorite settings, please login to your accountto see settings we have programmed for you or make updates,” or othersimilar notifications via the vehicle or to any connected device overthe Internet.

In other cases, notifications may not be sent. In some cases, thesettings will just occur automatically. In some examples, notificationscan be provided with a link or access to a user interface of anapplication. Via the application, the user can manage, set, control orview any aspect of the connected vehicle. In some cases, the settingscan be manually adjusted by the user way from the auto settings. In suchcases, the manual setting can be learned and can be provided moreweighting since the user took the time to correct an auto setting. Thus,various levels of weighting or importance can be given to learnedsettings. In other embodiments, the learned settings can be comparedagainst learned settings of other vehicle owners having access to cloudprocessing. Using data from these different user profiles, learnedsettings can be obtained or generated.

Generation or analysis can be by way of overlap processes, clusteranalysis algorithms, Connectivity based clustering, centroid-basedclustering, clustering model most closely related to statistics is basedon distribution models, cluster validation, density-based clustering,KNN/profile similarity, collaborative filtering, content-basedfiltering, hybrid recommender systems, mobile recommender systems,cross-sectional analysis, similarities in particular data types orsettings, concentration in similar settings by particular demographics,and other similarity analysis calculators and aggregators. Thesesettings can then be recommended to the user or can be automaticallyadded to the profile. Recommender systems can the user the analyzed datato generate the custom recommendations for settings to users' profiles.

FIG. 16A describes an ecosystem where an APP 104 in conjunction with avehicle API 130 may work together to make assumptions, make decisionsand take actions 2200. API and APP code together can be arranged in sucha fashion that creates an assumption and reasoning logic module 2216.This Assumption and reasoning logic module can take inputs from varioussystems and data streams including but not limited to GPS 2206,calendars 2208, traffic conditions 2204, local news 2202, past data ofuser behavior and interaction 2210, vehicle diagnostics 1926, userpreferences 2214, user login profiles 506, environmental interpretationsby sensors 2212, marketing deals 2224 among others. These inputs can belocal and physical or remote and abstract via a network. The assumptionand reasoning logic module 2216 compiles data from these sources toinvoke decisions and actions on a decision and action engine 2218.

This decision and action engine 2218 has the ability to execute on whatthe assumption and reasoning logic module has determined needs to bedone. The decision and action engine has the ability to produce alerts,both local, on screen, audibly, visually or remotely on a remote displaydevice 210 a-e using a data network. The decision and action engine 2218also has the ability to change vehicle controls automatically on behalfof a user without user action based on assumptions made by theassumption and reasoning logic module 2216. Additionally, the decisionand action engine has the ability to request a decision from the userpreemptively in order to change vehicle controls.

This may be achieved locally or remotely requiring input from a user toproceed. For instance, the assumption and reasoning logic engine hasdetermined that the user may want to have his or her car automaticallystarted at 7:55 am because the user typically starts the car at 8 am.Starting the car at five minutes early will allow the system to heat thevehicle to the user's typical liking. However, the assumption andreasoning logic may have only reached a level of confidence of 75% where80% confidence is required to act without user input. Thus, the system,being only 75% sure that the car should be turned on will automaticallysend the user an alert requesting a decision on whether or not to turnthe vehicle on. Once the user 121 provides an decision remotely on theirremote device 210 a, the decision engine 2218 updates the assumptionmodule 2216 so that it can augment it's assumptions for an updated levelof confidence on the next action trigger. These actions by the userautomatically and continually update the assumption and reasoning logicmodule 2216 in order to fine tune the level of confidence on actingwithout user input and learn the user's behavior for future decisions.

FIG. 16B describes how one of many types of inputs into an assumptionand reasoning logic module 2216 can be compiled over time. Althoughinputs can come from many sources, this particular example focuses oninput into the assumption and reasoning logic module 2216 from past dataoriginating and triggered by user behavior in order for module 2216 tolearn. Past actions 2210 are logged into a database either locally onthe vehicle computer or remotely which are fed into to module 2216. Inthis example, data about when the user's actions are stored, along withunique identifiers that will allow assumptions to be made in the future.

These identifiers include times, dates, rates, capacities, temperatures,frequency, degrees, distance, etc. In this example, the system has beenkeeping track of when the user has been starting his or her engine inthe morning on weekday sand weekends. The system harvests all datapoints associated with given events. These data points 2210 are purelymined data points and no assumptions or reasoning occurs at this point.This data will be used by the assumption and reasoning logic 2216 todetermine future actions.

FIG. 16C describes one example of what an assumption and reasoning logicmodule 2216 may produce using the data points collected on an ongoingbasis in FIG. 16B. Over time, using inputs that are continuallyharvested by a user's action, assumptions are made and refined to aid inmaking decisions for a user in advance or behalf. Module 2216 has takenthe inputs provided by 2210 past data and behavior to determine thatbefore a decision can be made, the user's local or network-storedcalendar should be polled to determine how the user's schedule mightimpact the system's pending actions. For instance, if the system haddetermined that the user typically starts his vehicle at 8 am but theuser's calendar shows a meeting at 730 am located at a location thatdoes not match the current location, the vehicle may assume that the carshould be started at 725. They system will determine its level ofconfidence of the decision and may poll the user for a decision.

The system, by using prior data points has stored assumptions based onconditions, the day it is, the temperature of the environment andhistorical events, that the user will most likely start the vehicle'sengine between 803 am and 805 am, and if the temperature is in the 30sinside the vehicle, the user will most likely set the interiortemperature to between 70 and 80 degrees, it is not likely that the userwill use the are conditioning unit, if there is ice on the windshield,the user will most likely defrost the windshield for 7 minutes beforedeparture, the user usually drives between 15 and 18 miles at this timeof day, the user typically starts the vehicle again in the afternoonbetween 505 pm and 510 pm, if the temperature is in the mid 70s, theuser usually activates the AC and sets the temperature to 65 degrees,typical weekend behavior, the user typically makes frequents stops, doesnot have a set time the vehicle is started, uses certain APPs at certaintimes and has a history of certain destinations as recorded by GPS.

FIG. 16D describes an example list of decision the decision and actionengine 2218 may take based on information provided by the assumption andreasoning logic module 2216 and sets of assumptions created. Thedecision and action engine 2218 will attempt, using a degree ofconfidence to anticipate what the user will want to do in terms ofengine start and stop, location destinations, preferences oftemperature, driving habits and poll vehicle capacities to ensure theintended path the user usually takes is attainable. For example, theuser usually drives a distance in the morning at a certain time,however, the vehicle's fuel supply will not allow for that distance tobe traveled. Thus, the decision and action engine polls the user as areminder that the user should begin their intended travel sooner thanusual to allow for refueling time.

In one embodiment, at a remote location, a user is able to access a userinterface for an application, which provides users access to useraccounts. A user account can be for a user and the user can add one ormore vehicles, objects, data or appliances for remote reporting, viewingand control. In one embodiment, a user is an owner or user of a vehicle.The user can register the vehicle with a remote service.

The remote service can be accessed over the Internet, such as via awebsite or application of a portable device. The remote service canprovide a multitude of cloud services for the user, such as remotecontrol features, remote viewing services, remote alarm controls, remotecamera activation, remote audio/video recording of the vehicle (i.e.,areas around the vehicle and inside the vehicle). In one embodiment, thevehicle is able to connect to the Internet (e.g., when the vehicleengine is off, on, and/or is occupied or un-occupied) to allow a user,via a remote cloud service, to access features of the vehicle. Thevehicle can be accessed when running, when parked, when stopped, whenmoving, etc. The vehicle and its audio recording devices and videocameras can be accessed from remote locations, to allow users toremotely communicate with the vehicle or with people riding or residinginside the vehicle.

The remote communication can also allow a person to communicate remotelywith people standing outside (or inside) of a vehicle. For instance, ifa user is accessing his or her vehicle from a remote location, camerasinstalled in and/or on the vehicle allow the remote user to see a personstanding proximate to the vehicle. The remote user can then communicatewith a person standing proximate to the vehicle using microphones andspeakers of the vehicle.

In some embodiments described herein, vehicles, structures and objectsmay include circuitry and communication logic to enable communicationwith a cloud processing system over the Internet.

In one embodiment, the services provided by the electronic systems of avehicle can include services that access the various components orsubsystems of a vehicle, such as door locks, service histories, userprofiles, audio settings, entertainment settings, mapping functions,communications systems, telecommunication synchronization systems,speakers, heating and cooling functions, auto-engine start/shut-offremotely via smart devices, remote heating/cooling initiation, remoteface-to-face conferencing, etc. The electronic systems within a vehiclecan also provide a user interface, such as a graphical user interface.The graphical user interface can include a plurality of buttons,controls and transceivers to receive input from a user.

The input from a user can also be provided by voice input, facialrecognition, eye-retina scans, fingerprint scans, a combination ofbiometrics, or via a capacitive or regular touchscreen contained ordisplayed within the vehicle, the vehicle's glass, doors, dashboard,etc.

In one embodiment, vehicles can maintain information regarding wherethey are, where they are heading and their destination maintained whichis maintained by GPS and navigation systems on board. The informationcollected and maintained by every vehicle may be mutually exclusive,meaning that only each individual vehicle is aware of its own heading,rate of speed and current location. This information, in one embodimentis crowd sourced and/or crowd shared/consumed for use in for accidentavoidance or other communication. By networking vehicles within acertain radius together, all individually location-aware vehicles becomeaware of all other vehicles in their sphere of influence. Vehicles maynetwork with vehicles in their range using wireless communicationsystems such as but not limited to Wi-Fi, Wi-Gig LTE, cellular, radio,near field communication or other methods.

In one embodiment, the communications of the vehicle and electronics ofthe vehicle will enable direct communication with a user of the vehicle.The user of the vehicle can include, for instance, the owner of thevehicle, a driver of the vehicle, or any third party having access tothe vehicle (either to drive the vehicle, to monitor the vehicleremotely, etc.)

The access to the data can also be encrypted to prevent unauthorizedaccess to the data. GPS and mapping services can also be incommunication with the cloud processing 120 provide data concerning thelocations of the vehicles and activities that occurred to the vehicleswhen at particular locations. The cloud processing 120 can be access bythe vehicles themselves using their electronics and communications, viamobile devices, from home, from work, etc.

In some embodiments, the vehicles may establish peer-to-peer links tofacilitate fast transfer of data. In other embodiments, vehicles maylink to each other using pairing algorithms that allow the vehicles toexchange data using WiFi, Bluetooth, near field communication (NFC), orsome other short range communication protocol.

A user's APP homepage may also include dynamically updating sections inwhich the most important information at a given time may be displayed orsurfaced to a user. If a user has parked in a certain parking area, heor she may want to monitor metrics related to incidents that may haveoccurred to his or her vehicle, vehicles around his or her vehicle, anydynamically received alerts, as well as precaution levels. Additionally,a user may choose to configure his or her APP homepage to display themost pertinent audio and video feeds to their needs.

In one embodiment, the vehicles can communicate directly with each othervia a temporary pairing process. The temporary pairing process can beautomatically enabled when vehicles become too close to each other, forexample. When this happens, local communication between the vehicles,such as a peer-to-peer connection, Wi-Fi connection, NFC connection, orBluetooth connection can be established to enable the vehicles to shareinformation concerning their proximity to one another.

This local communication will enable one or both vehicles to takecorrection actions or alert a driver to change course or triggerautomatic collision prevention measures (e.g., more aggressivenotifications to one or both operators, slow the speed of one or morevehicles, change the driving direction of one or more vehicles, etc.).Once the close proximity communication occurs and some corrective actionis made, the data regarding the occurrence and the actions taken can becommunicated to the cloud system for storage. The information can thenbe viewed by a registered user having access to an account for thevehicle(s).

FIGS. 17-30B define methods and systems for assigning advisor accountsfor accessing data regarding the vehicle, and also describe the use ofelectronic keys (e-keys), in accordance with several embodiments.

In one embodiment, users of vehicles may wish to provide advisors withaccess to select data associated with a vehicle. For example, a vehicleowner may decide to make a user account for an advisor. The advisor, inone embodiment, can be any person or entity. The advisor, in oneembodiment, may be a service person, a dealership service department, amechanic, an auto shop, a consultant that provides auto advice, or afiend of the vehicle owner. In one embodiment, an owner of a vehicle candefine particular aspects of the vehicle data, as being available forproviding or sharing with an advisor. The aspects can include, forexample, maintenance type information or vehicle status.

Other aspects can include, without limitation, engine indicator data,tire status, tire air pressure, oil level, transmission fluid level, oilgrade level, electric vehicle battery status, battery charge level,battery faults, temperature over heating data, service date expiration,mileage data, next service time, coolant level or status, transmissionfaults, air filter state, wiper change/status, brake pads, brake fluid,tire rotation, remote diagnostics requests, history data, etc. In oneembodiment, a user of a vehicle can define or establish an advisoryaccount, which will be provided with limited or select access tospecific vehicle data, so that the advisor can process the data andprovide recommendations to the user.

For instance, certain vehicle data can include data that is not personalor sensitive. The vehicle data can then be used by the advisor toprocess the data, examine the data, and based on some expertise orknowledge, the advisor can provide some recommendation to the user. Therecommendation can include, for example, notifying the user that thevehicle needs some service or action. The recommendation can include,for example, sending the user information regarding the recommendationand suggesting available times, dates, etc., to allow scheduling of anappointment.

In one embodiment, the communication from the advisor can be in the formof an email, a notification, a phone call, a text message, orcombinations thereof. The communications can include, for example,icons, links or graphics to allow the user to accept a schedule time forbrining in the vehicle for service. In one embodiment, when the enginelight comes on, the advisor is notified, and the advisor can contact theuser to tell the user that the engine light is critical or not, and theadvisor can be allowed to do remote diagnostics to better define thesignificance of the engine light warning. The advisor can then providemore informed advice to the user. In one embodiment, the advisor accountis limited to the predefined data that the user wishes to provide accessto.

In one embodiment, when the advisor is given an advisor account by auser, the advisor may be provided with an email, link, phone number,text, message, etc., which will allow the advisor to login to an advisorportal of cloud processing. The advisor portal will provide the userwith a website that shows the current vehicle status for each of thevehicles that the advisor is monitoring or for which the advisor wasprovided an advisor account.

The advisor portal will allow the advisor to set logic or rules to bealerted when certain types of important data is received for particularvehicles. For instance, if the advisor is monitoring a plurality ofvehicles, the advisor may wish to know when particular vehicles see aparticular type of fault or error, which may be important enough for theadvisor to handle immediately. The advisor may see that a certain user'scar is running too hot, the advisor may be notified or alerted so thatthe advisor can contact the user of the monitored vehicle. The advisorcan execute or cause to execute remote monitoring procedures to querythe vehicle to see what other condition are, so that a properrecommendation can be provided.

In one embodiment, the user can add a mechanic or auto repair shop andassign them an adviser account. The adviser account would get access tospecific vehicles (that pre-allow access), and the user can definespecific vehicle data for which access or privileges are provided. Forinstance, as a user drives around, the car may detect a fault, and theadviser may get a message or notification regarding the fault. Theadviser can then communicate with the user to provide his/her technicaladvice, recommend actions to take, recommend to come in for service, orthe advisor can pre-order a part needed for the service, or notify theuser that a part of the vehicle is defective or is on recall.

The adviser account can be defined for auto dealers, mechanics, servicestations, persons having vehicle knowledge or expertise, etc. Dealersthat provide service (e.g., service departments) can receive selectednotifications regarding the vehicle health, and based on the degree ofseriousness, the dealer/service center can ask you to bring the car in.Currently, dealers rely on users to notify them when warning lights gooff. If the problem is serious, and the driver ignores the warninglights the car can get damaged. In one embodiment, these methods/systemsprovide ways to share specific vehicle maintenance data with selectentities. The reporting by the car can be saved to a log/database ofevents that are reported, and the adviser/dealer can reply to thenotices to communicate instructions or recommendations.

FIG. 17 illustrates a block diagram of a process where a vehicle (CAR-A)is associated with vehicle data, settings and control 500, and thevehicle is connected or connectable with the Internet and cloud services120. In one embodiment, the vehicle can produce a plurality of types ofdata, such as vehicle status, vehicle service, vehicle location, vehicleusers, and vehicle control, etc. The type of data that a vehicleproduces can essentially be limitless, and will depend on the type ofvehicle, activity of vehicle, the types of users, the location of thevehicle, features the vehicle, use of the vehicle, etc. Additionally,various aspects of the vehicle can be controlled remotely via theInternet, and through cloud services 120 in response to control systems,algorithms, methods, circuits, and the like.

In one embodiment, cloud services 120 can include a customer accountdatabase that includes a plurality of customers. Customers may becustomers that have registered with a service that manages or provideaccess to features of a vehicle. The service may be a separate companyfrom a dealer, or it may be a dealership, it may be a car servicecenter, a private service, a friend, or an Internet service, etc. In oneexample, the customer database has is a plurality of customers that haveregistered with the service to enable issuance and management of useraccounts for their vehicles that have been registered with theservice(s).

In this example, the customers include customer A, customer B, customerC . . . customer N. In one embodiment, each customer may register one ormore vehicles for the service. For example, customer A is shown to havetwo vehicles 502 (CAR-A and CAR-B). For CAR-A, the customer may haveuser accounts 504. The user accounts 504 can include different types ofaccounts. One such account can be those associated with drivers that maybe driving the vehicle. The drivers will each have different roles,which defined the type of user and associated privileges. For example,one user may be administrator (admin), wherein administrators areusually the owners, the person that leased the vehicle, or a person thathas some control over the vehicle. In other embodiments, theadministrator may be the dealership for the service provider.

Other users can be assigned as drivers, such as teenagers of the family,valet drivers, guest drivers, etc. Each of these drivers can beassociated with their own user account, which provides specificprivileges (use capabilities, restrictions, limits, parameters, etc.).In another embodiment, user accounts viewed as advisors 506 can also becreated. As noted above, advisor accounts are those that provide thirdparties with access to the vehicle or access to data about the vehicle.Such parties can include dealerships, mechanics, service people,personal advisors, friends, etc. Each advisor account can be assigned adifferent role, which is linked to a level of privilege. The moreprivileges that are provided to an advisor account, the more data thatthe advisor can receive, access, or control.

In one embodiment, if the dealer is an advisor having an advisoraccounts, the owner the vehicle can define the level of privilegesprovided to the dealership. The level of privileges can identify whataspects of the car the user wishes to allow the dealership to know or bemade aware of. For instance, the advisor account can set that thevehicle will automatically provide certain data to the dealership. Suchdata can include the status of the vehicle, engine light data, healthinformation about the vehicle, malfunctions of the vehicle, serviceinformation of the vehicle, etc. However, because the advisor accountcan be specifically tailored to only provide certain information andprivileges to the dealer, the owner or admin of the vehicle can definethe specific advisor accounts to share only certain sub-sets ofinformation.

For example, certain information that would likely not be shared caninclude, location of the vehicle, history of routs of the vehicle, radiostation data, Internet communications, camera data, voice data, or otherinformation that may be private or sensitive to the user. Of course,this information can be shared if desired. In essence, the advisoraccount can be defined to provide only the information that the userwishes to share with that specific advisor. This allows for informationsharing about the vehicle to be spliced down to the specific feature anddata and the specific recipient of the data via the advisor account.

Thus, the information can be parsed to various advisors, by definingmultiple advisor accounts. For instance, the user can define an advisoraccount for a tire dealership and a separate advisor account for an oilchanging service station (e.g., for the same vehicle). The vehicle canthen automatically transmit data to the service provider, or cloudservices, which can then allow the entities associated with the advisorcounts to see the data coming from the vehicle or posted by the vehicleto a website. The operators of the services for which the advisoraccounts were assigned can then communicate with the user and provideadvice regarding the operation of the vehicle, information aboutupdates, warnings, service scheduling, or provide for remote access tothe vehicle diagnostics and make changes when necessary.

Therefore, by providing this level of detail to specific advisoraccounts, the user can predefine what type of data will be shared withthe advisor accounts while not sharing data that is sensitive to theuser, administrator, owner, or proprietor of the vehicle.

In one embodiment, cloud services 120 will be defined by a plurality ofservers, storage, dash-board data websites, graphical user interfaceAPIs, processors, user interfaces, and the like. The configuration ofservices offered via cloud services 120 can depend on the serviceprovider. As noted above, the service providers can include any numberof entities. Entities can include car dealerships, service providers,mechanics, private entities, individuals, etc.

In one embodiment, the service provider operating a cloud service 120can include a vehicle interface 508. Vehicle interface 508 is logic thatwill enable cloud services 120 to communicate with the electronics andsoftware with specific vehicles. Different vehicles have different APIs,systems, software, firmware, etc., and the vehicle interface 508 canfacilitate the handshake between cloud services 120 and a specificvehicles. Vehicle interface 508 can include database 512 for vehicledata. Additionally, the vehicle interface file a can include or havecontact with vehicle control logic 510, which manages the interfacingwith the specific vehicles. For example, if one vehicle type requires aspecific algorithm, packet structure, API, etc., the vehicle interface508 will utilize that communication protocol.

Vehicle control logic 510 can further provide the APIs and commands thatare necessary to provide or obtain information associated with thevehicle. The information can requests for data from the vehicle, and caninclude instructions to the vehicle to perform certain executable tasks.Executable tasks can include, for example, running diagnostics, testingcomponent parts or functions, communicating with occupants of thevehicle, etc. Cloud services 120 can also include logic for managingprivileges 514, which can interface with user account settings 516 andcan also manage the access and notification requirements or privileges518.

Accordingly, each of the customer accounts can include a plurality useraccounts, and each of the user accounts can be associated with specificuser account settings that define the privileges for that account,whether it be a driver account or an advisor account.

FIG. 18 illustrates an example a vehicle being associated with advisoraccounts 506 and driver accounts 520. Advisor accounts 506 can include,for example a dealership, a mechanic, and other entities that will haverestricted access to data of the vehicle or specific suites ofinformation regarding the vehicle and/or access to communicate orcontrol features functions or parts of the vehicle from a remotelocation.

The drivers 520 can also include a plurality of drivers, which may havepredefined access to the vehicle. Some accounts can also be associatedwith temporary drivers, such as valets, mechanics, service people,friends, etc. In one embodiment, the driver can place the car in thevalet account mode when the vehicle is provided to a valet for parking.In the valet mode, the vehicle will have restricted use parameters, andwill also provide for reporting back to the user in case violationsoccur in accordance with the predefined privileges assigned to a valet.Examples of violation can include, driving too fast, driving out of anarea, accelerating too fast, stopping too fast, parking too close to astructure or other vehicle, coming in contact with a structure oranother vehicle, slamming the door, turning on the radio, changingpersonal user settings such as seats and mirrors, etc.

Cloud services 120 can therefore assign the advisor accounts and thedriver accounts accordingly and manage the privileges associated withthose accounts. The cloud services will also enable efficientcommunication with the vehicle to provide and place/set the variousaccounts at different times.

FIG. 19 illustrates an example of a computing device, which may have aplurality of user interface icons for assigning new driver accounts 532,or advisor accounts 538, in accordance with one embodiment of thepresent invention. Using Add driver account 532, the user can definedthe roles of the driver 534. The roles of the driver can also include aset of privileges 536. For example, the driver account can be for ateenager and the role can be set to limit the speed, or providenotifications when the teenager has driven the car beyond a particulararea or geographic location.

The privileges can also moderate access to the speed of the vehicle, andused during specific periods of time. For setting an advisor account,the user can set advisor account and defined the roles 540, and set theprivileges 542. The diagrams on device 530, maybe part of a userinterface that includes icons and buttons that allow the user to select,edit and add accounts, or management of the accounts that the previouslyset.

Accessing the accounts that have been previously set can also allowaccess to the history database. The history database can includeinformation regarding the use of the vehicle when the vehicle wascontrolled under a specific user account, or the types of actions takenby an advisor via an advisor account. Access to these user interfacescan also be through a website provided by the service provider. Thewebsite can provide access to the user by user name and password, orother credentials. This access will therefore be tied to a user account.The user account can include identifying information of the user, thevehicle, privileges, encryption keys, etc. The user, upon access, canview the historical use of the vehicle, assign new accounts, revokeaccounts, remove accounts, store historical information, and communicatewith holders of the accounts.

For instance, the user can log in to website and communicate with theiradvisors if advisers had left a message for the user/owner of thevehicle. In one case, the advisor account of a dealership may have lefta message for the owner indicating that the engine light is on and thevehicle must not be driven due to a recall. Via the website, thedealership may propose certain dates for the service or an appointmentto have the vehicle picked up or serviced. These messages may also betransferred to the users mobile device, and urgent communications can besent by e-mail, text, notification, phone calls, voice messages, or anycombination thereof.

FIG. 20 illustrates an example of an advisor account 550, where the userhas selected the type of user for that advisor account 552, inaccordance with one embodiment of the present invention. In thisexample, the user may select the type of advisor account to be for amechanic, a dealer, a service station, service center, a dealer insales, a third party, etc. For this illustration, the advisor accounts550 is for a mechanic, and the user can defined the role 554 of theadvisor account when mechanic. The mechanic may be given access tospecific features of the car but not access to other features of thecar. The features can be associate with different levels of privileges,and the user can use selection buttons, icons, tick boxes, radiobuttons, touch screens, keyboards, etc., to select some or all or noneof the specific privileges for each of the types of functions or actionsor data that may be accessible or usable by the mechanic using advisoraccount 550.

For illustration, the roles 554 can define access the various features,for example engine light, oil level or pressure, battery status,electric powertrain, phone lists, temperature, cooling system, chargingsystem, radio settings, entertainment settings, geo-location data,historical data, advisers history, etc. This listing of features orinformation regarding the vehicle is only exemplary, and should beunderstood that more features can be accessible depending on the type ofvehicle and the type of features provided by the vehicle. Additionally,the advisor account can be associated with specific ones of the featuresand for each feature that is associated with the advisor account, thelevels of privileges can also be defined.

FIG. 21 illustrates an example where a user having an advisor accountscan communicate with an advisor application to receive advisor dataregarding the vehicle. The advisor data is data that is provided by theadvisors in response to the advisor receiving data from the vehicle. Thedata from the vehicle, in one embodiment, is automatically sent by thevehicle over the Internet/cloud services 120. As discussed above, thetype of data sent to cloud services from the vehicle will depend on theadvisor account and the privileges for the specific features and/orcontrol provided to the advisor user. As shown, advisor data 559 istransferred to cloud services 120. Cloud services will receive theadvisor data 560, and it will process the advisor data using advisorlogic 562.

In one example, the advisor logic 562 will include programs that willdefine what will happen to the data that is received. Some of thereceived data will be processed to generate recommendations, some datawill be processed and added to a log, some data will be send andprocessed to automatically notify the vehicle owner about a vehicleevent. Certain of the data will produce or require that action items bereported to the advisor. Advisors will receive data 566 from thevehicles that were assigned to the advisors, and in return the advisorscan provide feedback to the vehicle owners.

In some embodiments, an advisor will have advisory accounts from manyvehicles (such as a dealership advisor), and the dealership can providefeedback to the different vehicle owners. Advisor responses and advisorfeedback is then forwarded to the user in operation 568. This forwardingof the advice can include automatically generated notifications,messages, or custom notifications as feedback based on the advisor data559 received from the vehicle over time or for one event. The vehicleowner or user will then receive advice 570 from the advisor accountreporting back to the user, based on the data provided by the vehicleautomatically, based on the advisor accounts.

FIG. 22 illustrates an example of various vehicles in communication withcloud services 120. Cloud services 120 is also in communication withvehicle users 586 and advisors 588. The type of information receivedfrom vehicles can include any number of metrics associated withfeatures, functions, parts, operation, etc. For purposes of exampleonly, some system features can include engine oil, tire rotation, tirehealth, oil filter, battery, brake pads, wipers, coolant, transmissionfluid, air filter, remote diagnostics, etc. Cloud services can include anumber of operations and systems and programs that operate on the data,notify vehicle owners, receive data from vehicles, hold and exchangedata between advisors and vehicle owners, etc. In one example, cloudservices can include an operation where a database storage vehicle statedata 574 is managed.

Additional data can include advisors settings and user defined settings576. Also included are privileged verification modules 578 which assignprivileges to the various user accounts and manage enforcement of theprivileges defined by the users for each of the various accounts.

Advisor account logic 580 is also provided, which allows advisors thecustom defined what programs, actions, or operation will take placeeither automatically or require notification to the advisor when vehicledata is received from vehicles placed in their advisor care. The advisoraccount logic 580 can also provide access to the advisors via website,which allows advisors to view, access, communicate, adjust, control, andinterface with features that were provided by the user in the privilegesfor that advisor account.

The advisors not having access to certain features, as defined by theadvisor account will not be allowed access via the website and theadvisor account logic 580 will restrict that access. Advisornotification logic 582 is also provided, which provides forcommunication modules that will interface between the user, the vehicle,and the advisor. The communication modules can also include interfacesfor communicating with users via third-party applications, such ase-mails, notifications, social media, text, web applications, andgeneral messages.

Advisors module 584 is also provided, which provides for management ofthe advisor accounts, creation of advisor accounts, management ofadvisor feedback logic, and historically tracking actions taken or nottaken by advisors using the advisor accounts 584 on specific vehicles.

FIG. 23 illustrates an example where a plurality of vehicles 586exchange advisor account data 590 with cloud services 120. Cloudservices 120 will then communicate with the various advisors 588. Theadvisors and be an auto shop, such as Roy's Auto, a dealership, a carcare service, etc. The various owners of the vehicles can thereforedefine specific advisor accounts for different types of features,functions, or parts of the vehicle. Data seen from the advisors 588 istherefore provided as advisor feedback to the users 592. The advisorfeedback can include recommendations for service, scheduling ofappointments, providing advice, providing remote diagnostics, providingmessages and notifications to the users that assigned the advisoraccounts. The communications, messages, notifications from the advisorswill then be sent back to the vehicle users 586.

Accordingly, data is passively sent from the vehicles to cloud services120 as the advisor account data 590, and only specific data is sent tothe specific advisor accounts. The advisor accounts will receive onlythat data identified by the privileges set in the advisor accountsassigned to them by the vehicle users. The vehicle users will thenreceive information back from the advisors, as set by the owners/adminsof the vehicles. Some owners/admins may only use one advisor account fora limited feature, such as oil changes, and no more. This is possible aswell as the other extreme where many advisor accounts are set up fordifferent parts or same parts of the vehicle.

FIG. 24 illustrates an example of an advisor portal 600. The advisorportal 600 may be a website provided to an advisor that has beenprovided an advisor account by a vehicle owner Bob 604, which is acustomer 602. Bob may have various cars set up with advisor accountswith the same advisor. For the specific cars that Bob has assigned tothis advisor, the advisor can view specific information regarding thecar and can provide communications back to Bob regarding the car. Inthis example, the advisor can view current vehicle status 606, vehiclefaults 608, warning lights 610, recommended actions 612, and caninterface with the information via graphical user interfaces to exposemore data if privileges were provided. The advisor can also providespecific communications to the vehicle owner Bob. A note to Bob 614 canbe generated to notify Bob that his car is low on oil and recommends aservice. Bob can also be notified that the warning light is on and canprovide a recommended/appointment date and time 616. The message canalso be sent to Bob regarding his brakes, along with a recommendedscheduling time 618.

Cloud services 120 can then communicate the advisors responses to Bob,and the car can communicate car data back to cloud services 120. In thismanner, information that is traditionally only stored in the vehicle andaccessible when the vehicle is taken in for service can now beautomatically transferred to those advisors that have knowledge aboutthe vehicle and can provide feedback in substantial real-time.

FIG. 25 illustrates an example where Bob utilizes cloud services 120 toassign multiple and different advisor accounts for the same vehicle. Inthis example, an adviser account has been set up for an oil servicestation 620. Advisor account has been set up for a tire shop 622. Andadvisor account has been set up for a dealer 624. Because advisoraccounts can be set up for specific parts or functions of vehicle, ispossible to assign specific advisor accounts for specific functions ofthe vehicle, while excluding other functions. The advisor account forthe oil service station will not have access to the tire information ofthe vehicle. In this example, the tire shop will likewise not haveaccess to the oil service information of the vehicle. Cloud services 120will manage sending only the information that relates to that specificadvisor account to their advisor accounts, and in accordance with theprivileges. Advisor accounts are assignable 626 to different entitiesfor different categories of vehicle modes, vehicle parts, vehicleconditions, vehicle states, etc.

FIG. 26 illustrates an example where the vehicle owner Bob has assignedadvisor account to a valet, in accordance with one embodiment of thepresent invention. Using cloud services 120, Bob can utilize his mobiledevice to assign on the spot an advisor account to the valet, who willutilize his or her mobile device to access the vehicle. It is example,the advisor account is able to transfer electronic keys (e-keys) to thevalet for use via his mobile device. In operation 628, Bob assigns atemporary advisor account to the valet. In operation 630, the accountwill provide the valet with access the vehicle, such as forunlocking/locking and turning on the vehicle. In this example, metadatasets the level of privileges for the vehicle during the use of theelectronic keys.

FIG. 27 illustrates an example where electronic keys are assigned to anadvisor account. In operation 632, that entity that is to receive anadvisor account is identified. The identification of the entities can beby way of sending an entity e-mail, a text message, a notification, anear field communication (NFC) signal, a bump signal, a Bluetoothsignal, a WiFi signal, or some electronic transfer signal or signals. Inoperation 634, the privileges are set for the advisor account, wherespecific vehicle aspects are enabled for the vehicle.

Information regarding data reporting can be set, remote accessprivileges can be set, local access can be set for using the vehicle(such as starting the vehicle opening the vehicle, locking the vehicle,unlocking the vehicle, restricting speeds, restricting distances, etc.).In operation 636, the advisor account is generated. The advisor accountis then sent to the target recipient in operation 638. Sending theadvisor account to enable use of the vehicle, in one embodiment includessending encrypted e-keys to the recipient.

The target recipients can be the person to which the advisor account isbeing set. For example, the advisor account can be for a mechanic, adealership, a service station, a valet attendant, a person, acorporation, and entity, etc. In the case of the valet, the advisoraccount can be sent to the recipient user or person working at the valetstation. The valet account will then be received operation 639. Thevalet account will provide access 640 to the vehicle. As noted above,the access may include unlocking the vehicle, enabling starting of thevehicle, locking the vehicle, etc. This will allow the valet to drivethe vehicle for the restricted privileges set by the valet account 642.During the use of the valet accounts, the vehicle will maintain ahistory of the use of the vehicle and will provide reports or save theinformation to a log on a server or on the vehicle. In one embodiment,the vehicle can provide reporting 644 regarding any potential damage tothe vehicle while it was under the care of the valet.

In some embodiments, the valet account can be set using the vehicleelectronics. For example, the user can go to a screen of the vehicle,select the type of account which will enable use of the vehicle underthose privileges for a period of time.

FIG. 28 illustrates an example of the assignment of electronic keys(e-keys) by Bob to a valet. In this example, Bob utilizes his smartphone 652 to transfer electronic key 652 the valet's device 651. Thevalet's device 651 is the recipient of the electronic keys. In oneembodiment, the electronic keys transferred by Bob are sent to the valetby way of cloud services 120. For example, Bob can request that keys besent to the valet, and the request is sent to the server operating incloud services 120. The request can include information regarding theprivileges, limitations, and/or metadata associated with the request forthe electronic keys that are to be sent to the valet. The valet can thenuse the electronic Keys to use the vehicle in accordance with theprivileges set by the requesting user (Bob).

In this example, cloud services can maintain information regarding themonitored use of the vehicle during the assignment of the electronickeys to the valet. A history can be regarding the use. The history caninclude vehicle functionality, vehicle use, as well as occupantinformation such as camera data, audio data, exterior conditions, cameraconditions exterior to the vehicle, breach violations, attempted thefts,actual theft, damage data, etc. while the account is active. The issuinguser can also request that the account be deactivated, deleted, orturned off at any time. Reporting regarding the use of the vehicle canalso be managed by cloud services which will inform Bob of any activityor specific activity about the vehicle while the valet utilizes thevehicle using the e-keys assigned to the valet. The assignment of theelectronic keys can also have an expiration time, time frame, and anexpiration time or date or combinations thereof.

FIG. 29 illustrates an example where an owner of the vehicle Bob, isable to assign electronic keys (e-keys) 650 to any number of users. Thekeys can be assigned to users with various privilege settings.Additionally, the electronic keys can be sent to users that are remotefrom the user. For example, if Bob left his car at home, while at workBob can e-mail, text, message, or send electronic keys to a person thatmay need access to the vehicle that is remote from Bob. The user (e.g.,Bob) can be at a location remote from the vehicle or can be standingnext the vehicle or be in the vehicle when assignment of electronics ismade. In one embodiment, the electronic keys can be assigned to a numberof users, where the privileges are different for the same. Theelectronic keys for each user can be associated with a differentexpiration time and privilege priority level.

Each e-key, in one embodiment, will include a unique access code orsubstantially unique access code. The unique access code can begenerated by a server, such as cloud services 120. In other embodiments,the access code can be generated by the vehicleelectronics/logic/programs or can be generated by a mobile device orother computing system that is separate from a server. In otherembodiments, the access codes can be generated on a remote device fromthe server or on the server itself. The unique generation of accesscodes enables each electronic keyed to be different for each user andeach e-key can expire at any time set by a requesting user or can becanceled at any time from a device having access to the Internet.

Thus, multiple e-keys can co-exist. In one embodiment, if more than oneperson wishing to access or ride in the car has an e-key, one of thee-keys can open and turn on the car. If a user with an e-key havinghigher levels of privileges is riding in the car, the car can eitherautomatically transfer to the higher level or ask for permission totransfer privileges from higher level e-keys, even if the e-keys thatfirst accessed the vehicle were lower level in privilege setting.

FIGS. 30A and 30B are illustrative examples of having electronic keystransferred to a guest that requires access to the vehicle. Theelectronic keys 650 can be transferred to the vehicle and verified bythe vehicle or cloud services or both, before access is given to theguest. The communication by the guest to the vehicle can be performedusing any number of wireless communications, such as radiocommunication, Wi-Fi communication, Bluetooth communication, etc. Thedevice of the guest, who is the recipient of the electronic keys can beof any type of the device. Example devices can include smart phones,tablet computers, computer glasses, wristwatch computers, computerchips, thumb drive computers, or any other device having the capabilityof storing data, processing data, and exchanging data either wirelesslyor via some wired connection.

FIGS. 26-35 illustrate methods and systems for assigning e-keys forenabling access of a vehicle to a remote user, and related accountprivileges, as defined in several exemplary embodiments.

In one embodiment, a user can assign an ad advisor account to anyindividual. The Advisor account can be for any duration, and theduration can be set by the user. In one embodiment, the advisor accountcan be assigned to a guest driver of a vehicle. The guest driver can be,for example, a friend, a known individual, a service person, a valetperson or valet service, etc. The creation of an advisor account cantherefore be for a short duration, or long duration, or permanently, oruntil the account is canceled, stopped, revoked, expires, or eliminatedby the person/user that issued or created the advisor account. In oneembodiment, the advisor account can act to provide access to a vehicle.

In one embodiment, access can be by way of electronic keys (e.g.,e-keys), which can be sent by a vehicle owner/admin to some person orentity. For example, the user-owner of the vehicle can assign a valetwith access to the vehicle by going on an application (App or website)on a computing device (e.g., mobile or non-mobile device), identifyingthe recipient, identifying a mode for communicating with the recipient(e.g., text, email, message, notification, etc.), selecting the advisoraccount privileges (e.g., what type of access, speed limits, geographicrestrictions, amount of time the e-keys will be valid (or else expire)),and requesting that e-keys be sent to the recipient.

FIG. 31A illustrates an example where a user, John, utilizing his mobiledevice 702, is able to communicate and send e-keys to another user(Bob). In this example, the sending of e-keys will include the sendingof the request to a server, which may be operated by cloud services 120.At the server, the server will generate an access code for the vehicle(car—B). The access code will then be encrypted by the server and thensent as encrypted e-keys 722 to Bob's device 704. Bob's device 704 maybe a mobile device, such as a smart phone. The mobile device willinclude screen having interfaces and icons, and the ability to receivemessages, notifications, text messages, and e-mail. In one embodiment, anotification will be received by Bob indicating that John has providede-keys to Bob.

In FIG. 32, Bob utilizing his mobile device 704 will transfer theencrypted e-keys 720 to the vehicle that belongs to John (car—B). In oneembodiment, the receipt of the encrypted e-keys 720 will also includecode, logic, or program instructions that will request that the deviceID of Bob's device 704 should be transferred to the vehicle along withthe encrypted e-keys 720. At the vehicle, the vehicle will receive theencrypted e-keys and the device ID of Bob's device 704. The vehicle willhold a private key to unlock an un-encrypt the encrypted e-keys 720.

The encryption by the server of the-keys utilize a public key that isassociated with John's car, and held in or associated with an accountmanaged for John. In this manner, John's car, holding the private key inmemory can decrypt the encrypted e-keys 720. At the vehicle, thedecrypted e-keys will be bound, associated, or paired with the device IDthat transferred the e-keys in operation 730.

Because Bob transferred the encrypted e-keys 720 to the vehicle, Bob'sdevice ID is associated with the encrypted e-keys that were transferredto the vehicle. This will assure that future accesses using e-keys thatare activated for the car—B will be from the device 704 that receivedthe e-keys from the owner. The target device that receives the e-keys isthe recipient device that is identified by the user that requested thatthe e-keys be provided to the recipient. In operation 732, as mentionedabove, the vehicle private key is used to decrypt the e-keys to getaccess to an access code. The access code is the code that will enablethe e-keys to be activated e-keys 724. In operation 734, the access codeis bound to the device ID, as mentioned above. The access code is thensent as activated e-keys 724 back to Bob's device 704. Bob's device 704can now access the vehicle in accordance with the privileges set byJohn, the owner of the vehicle.

FIG. 33 illustrates an example where Bob utilizes his device 704 toactivate, open, lock, turn on, unlock, John's vehicle (car—B). Theaccess by Bob is facilitated by the activated e-keys 724, which are usedvia device 704 having the device ID that is paired or associated withthe access code associated with the activated e-keys 724.

FIG. 31B illustrates an example of operations that may be performed bycloud services 120 when a request to send e-keys to a recipient isreceived. Cloud services can receive the request 741. The request caninclude identification of the recipient and the privileges defined bythe requester for that issuance of e-keys to the recipient andidentification of the device that will receive the e-keys.

In one embodiment, the exact device that is to receive the e-keys is notidentified in advance, but only the communication modes to identify theuser. For example, the user may have multiple devices that can receivemessages. The device that actually receives the message and communicateswith the vehicle will be the device that will receive and be able to usethe activated e-keys when the transaction to use the e-keys is made withthe vehicle. Once the e-keys are activated on one device, the e-keyscannot be activated on other devices unless new e-keys are requestedagain.

In operation 742, the request is associated with the user account makingthe request. The user account will be John's account, which will havepredefined information associated with the vehicles that John is able toassign e-keys for. Additionally, the user account for John can alsoinclude templates that John can use to assign e-keys with variousprivileges. Some templates can be assigned to teenage users, spouses,mechanics, valet attendants, etc. In this manner, the user does not needto assign the specific individual privileges each time e-keys areassigned, but simply can assign a template of a group of privileges forthe specific assignment.

In operation 743, the server will generate a unique access code. Theunique access code can be generated by a number generator, andalphanumeric random generator, in incremental number generator, or anyother generation device that can generate codes that are unique orsubstantially unique. In operation 744, the access code is encryptedusing the vehicles public key, which is held by the server. The publickey held by the server enables encryption of the access code and anyassociated metadata, privileges, or communication data or codes, whichwill be sent to the recipient device for accessing of the vehicle. Inoperation 745, the encrypted e-keys are sent to the recipient. In thisexample, the encrypted e-keys 720 are sent to Bob and received by device704.

FIG. 34 illustrates examples of various assignments of e-keys 750 andthe generation of unique codes 752, as transactions between users andservers of cloud service 120. In the example shown, various e-keys canbe assigned by John to various different parties. Each e-key assignmentcan be associate with a different unique code generated by the server.Each unique code can then be used to associate those e-keys with thesame vehicle, but assigned to different devices/people with differentprivileges. The different e-keys having different access codes can thenbe encrypted and sent to the user for access of the vehicle.

In other embodiments, the access codes are not encrypted and will enabledirect access to the vehicle when the e-keys are sent directly to arecipient. In that embodiment, a user can send e-keys directly from onesmart phone to another smart phone or one device to another devicewithout the need for server involvement. Assignment of e-keys in thismanner may have lower levels of security, but the assignment of e-keyscan still be associate with uniquely associated access codes. The uniqueaccess codes can be generated by the mobile devices using applications,and expiration, cancellation or revoking of assignee-keys can be made orconducted via the mobile device (or any computing device, including theelectronics of the vehicle). In some embodiments, the mobile device willcommunicate with the server and in other embodiments no servercommunication will be needed.

FIG. 35 illustrates an example where a request is sent by John viadevice 702 to cloud services 120. Cloud services 120 can generate theunique access code which is then encrypted in a message and sent asencrypted e-keys 720 to the recipient, Bob, who receives it via device704. The request sent by the requester can include an action request.The action can be to send e-keys to Bob. The requester will identifyBob's contact data, such as e-mail, text, notifications, messages, NFC,etc. and can defined privileges for use. The duration that the e-keyswill remain active can also be set by the requester. Metadata definingthe active state of the e-keys can also be managed by the request,including deactivating codes or self-destructing access code routineswhen violations occur.

In one example, the app on the user's mobile device can request that amessage be sent to the recipient, so that the recipient can receive thee-keys and be granted access to the vehicle. In one embodiment, therecipient may have a mobile device or computing device (e.g.,smartphone, tablet computer, laptop computer, personal digitalassistant, smartwatch, computer glasses, or the like), on which acommunication can be received that provides instructions forobtaining/validating/using the e-keys. In one example, a message can besent to the recipient, which may provide instructions on how to activatethe e-keys.

In one embodiment, the message may have a link to an application thatcan be launched, which can be used to complete the activation and accesswith the vehicle. In another embodiment, a simple link can be sent,which when selected will link the user to a webpage, which providesinstructions for activating the access for the e-keys.

In one embodiment, application or webpage can identify that e-keys weresent to the individual recipient and will also identify the vehicle(e.g., brand, year, model, color, license plate, or more or less data),may identify the restrictions, and may identify the duration duringwhich the e-keys will remain active. After the duration (or earlier ifthe e-keys are cancelled by the user), the e-keys will discontinue towork. If, for some reason, the recipient still needs access to thevehicle, the original message or link can provide a method for allowingthe user to request more time. The user (e.g., owner of the vehicle) cantherefore, via the app or website, reactivate the e-keys.

In some embodiments, the e-keys when active will provide a graphicaluser interface on the device of the recipient, which may allow access,such as icon buttons to unlock, lock, start and stop the vehicle. Theapp can also send notifications to the recipient, if for example, theuser wishes to provide the recipient with more time or less time. Whilethe e-keys are active, in one embodiment, the vehicle can report backactivity of the vehicle, while under the care/use of the recipient. Theuser may have access to audio input or cameras, to communicate with thedriver/recipient. The vehicle use history can also be saved to a server,such that the recipient's use activity can be audited, or viewed oraccessed.

In one embodiment, the e-keys can be sent to any person, via acommunication message. The e-keys, in one embodiment, are sent to a userin a message so that the recipient can get a graphical user interfacethat allows the recipient to activate the e-keys and then open the car,turn on the car, drive the car, turn off the car, lock the car, etc.

For security purposes, e-keys are generated at a server, which may bemanaged by a server to execute cloud services. The server may receiverequests from registered users who may wish to assign e-keys to someindividual or entity. The request is associated to the user account, asmanaged by the service. If the user has multiple vehicles, the requestmay further include identification of the vehicle, such as CAR-A orCAR-B, etc. At the server, the server is configured to execute thegeneration of access codes for a particular request. The access codescan be uniquely generated by the server, for each received request. Inone embodiment, the access code format or form is set, so that a vehicleknows what to expect and reject access codes that do not meet the formator form. Once the access code is generated for the request, the accesscode is encrypted using a public key of the vehicle, which is assigned apublic/private key pair.

In one embodiment, the public/private key pair can be re-generated fromtime to time, if the user feels that a security breach has taken place.Usually, however, one public/private key pair may serve for a life of avehicle. The server keeps and maintains the public key and the privatekey is stored in storage/memory of the electronics of the vehicle.Although traditional encryption may make the public key freelyavailable, in one embodiment, the public key is only referred to as“public” for purposes of defining the encryption logic, but preferablythe public key is kept private or securely held by the server. Theprivate key can be stored or programmed when the vehicle is registeredwith a service or at any other time, when the public/private key pairare re-generated for security purposes. The transfer of the private keyto the vehicle can take place over any wired or wireless network, or bytransfer via some connector, plug, memory card, thumb drive, etc. In anyevent, the private key is stored and kept secure by the vehicle.

In one embodiment, in addition to the access code being encrypted, otherdata can also be encrypted along with the access code. Such other datacan include, for instance, metadata. The metadata may include a numberof control information/parameters, programming information, privilegesdefined by the requesting user, the expiration time of the e-keys,code/logic for self-deleting the access code of the e-keys on therecipient's device when the expiration time is reached, etc. In someembodiments, the device of the recipient, once the access code has beenactivated, can communicate with the server in a background mode. Thecommunication can include, for instance, having the server de-activatethe access code if the issuing user decides to cancel the access code.

For ease of discussion, reference will be made to encrypting the accesscode, but it should be understood that other data may also be encrypted.The encrypted access code is then sent to the recipient, as identifiedby the requesting user. The recipient will, in one embodiment, receivethe message that tells the recipient that he/she has received e-keys,and to click on a link or select a button provided or associated withthe message when the recipient is within communication distance to thevehicle. The recipient can then approach the vehicle, e.g., at wirelesscommunication distance (e.g., WiFi, Bluetooth, NFC, radio, etc.). Thedevice of the recipient, upon the recipient selecting the button orlink, will cause the device of the recipient to transfer the encryptedaccess code (e.g., e-keys) to the vehicle.

In addition, a device ID of the device that sent the encrypted e-keys tothe vehicle will also be received by the vehicle. The vehicle, becauseit has the private key of the public/private key pair, will be able todecrypt the access code. The vehicle will then bind the access code withthe device ID. The access code, being bound or associated with thedevice ID will be returned to the recipient's device, which will be theactivated e-keys. The activated e-keys will therefore allow therecipient, using the device with the device ID to use screens, graphicaluser interfaces, apps, or buttons on the screen or device to activelyuse the vehicle.

The activated e-keys will, however, only be active for the period oftime set by the vehicle owner that sent the request to grant the e-keysto the user. As used herein, the device ID can be any type of deviceidentifier, such as a model number, a code, a serial number, analphanumeric string, a numeric string, a simple number codes, or anytype of identifying data. In one embodiment, the device ID is a MACaddress of the recipient's device.

A cloud services website, which may be managing the generation of e-keyswill set metadata that defines what the limits or restrictions orparameters of the e-keys are, such as how long the-keys will be active.In one embodiment, the generation of the e-keys can be for a predefinedset period of time, e.g., such as 1 hour, 1 day, 1 week, 2 weeks, 1month, 1 minute, 2 minutes, 30 seconds, or until cancelled or eliminatedby the user. For example, the e-keys can be generated as a spare e-keyfor a person's wife or child. In that case, the-keys may not expire,until the account is cancelled, thus deleting the key pair validationand associated encryption.

In one embodiment, each e-key generated is unique, as the generatedaccess code was unique for the specific request. A random numbergenerator can be used to provide access codes. Each unique e-key, beingunique, can be cancelled and eliminated without affecting other issuede-keys. The number of e-keys generated can therefore be essentiallyunlimited, as each e-key is unique. In one embodiment, each e-keyassigned to a recipient can be associated with a log of activity. Thelog can identify what driving took place, where the vehicle was driven,speeds, damage sustained, radio stations listened to, conversations had,images of drivers during that time, etc. In some embodiments, the levelof monitoring can be more limited.

In some embodiments, the level of monitoring can be provided in amessage, at the same time the e-keys are assigned to a recipient. Inthis manner, each recipient will know in advance what monitoring isoccurring on the vehicle while the vehicle is used with the issuede-keys associated with the account or advisor account. In someembodiments, more monitoring will be acceptable, such as when thevehicle is driven by a valet. In some embodiments, less monitoring ismore acceptable, such as when a spouse is driving the vehicle.

The recipient user, in one embodiment will have a computing device forreceiving the e-keys. The computing device may be a phone, a watch, acomputer chip, or some processing device or storage. The recipient, oncereceiving the e-keys from a server can then access a link or icons on anapp or website of his/her device. The recipient is instructed to press abutton or select an icon or link to initiate access with the targetvehicle. The action taken by the recipient will cause data packets to betransferred to the electronics of the vehicle. The data packets caninclude, for example, the encrypted e-keys (e.g., having the accesscode).

The encrypted e-keys will be accepted and/or validated by the vehicle,and in one embodiment, can also include receipt of the device ID of therecipient desiring the access. Once validated, the recipient will haveaccess to the vehicle. The access may, for example, be in response tothe user selecting buttons, icons or app controls on his device, e.g.,smartphone or the like. Each time the device sends control data to thevehicle, the control data (e.g., to open the vehicle, start the vehicle,etc.), in one embodiment, the control data can be sent with the serveras well for tracking use.

As noted above, the e-keys can be assigned for any period of time, e.g.,such as a very temporary period of time or for a longer period of time.For example, a user can assign e-keys to a friend if the user is farfrom home and the friend needs access to the vehicle that may still beat home. The e-keys can expire, based on the defined period of time forthe e-keys. The e-keys can be managed by the user on a website, such asa site managed by cloud services. The user can see all e-keys that havebeen assigned in the past, which e-keys are active, deactivate anye-keys, see use history associated with any previously assigned e-keys,etc.

In another embodiment, a user can also receive notifications when avehicle is being accessed, driven or used in a manner that is inviolation of the privileges assigned to the e-keys. For instance, if thee-keys were assigned to a valet and the valet attempts to speedexcessively during the use of the e-keys, the user can be notified ofthe privilege breach or violation. In one embodiment, the accountassociated with the e-keys can act to automatically deactivate thee-keys upon detecting a violation.

In one embodiment, instead of waiting for a user to request that e-keysbe sent to a recipient, the recipient may directly request e-keys. Forinstance, if the vehicle is one that is from a car sharing entity, theuser may wish to access a particular car parked as some location. Thecar may be identified by serial number or some other identifier. Theuser, in one embodiment, using an application of the car entity canrequest e-keys. The request can be processed similar to when a usershares his/her keys with an individual. The requesting user waits forthe server to issue encrypted e-keys, which are transferred to thevehicle for decryption and verification. The vehicle can then issueactivated e-keys to the user for opening the car, starting the car,locking the car, etc. In one embodiment, the user can continue using thevehicle until a pre-determined period of time or during a time that theuser wishes to use the vehicle. Vehicle use can be communicated, for theused e-keys, back to the vehicle sharing entity. The vehicle sharingentity can then bill the user for the time used and any incidentals.

Accordingly, it should be understood that the issuing or sharing ofe-keys facilitates access and use of vehicles for any defined duration.It should be further understood that issued e-keys can also be issued tomultiple individuals at one time. For example, a vehicle owner can havean active set of e-keys on his/her phone. The vehicle owner may alsohave a set of e-keys active for a child of the home. The vehicle ownermay also activate e-keys for service people, mechanics, valet people,etc. These e-keys can co-exist and can all be active at any particularpoint in time. If both there are two users that wish to ride and/ordrive the car, the first user to activate the access via the e-keys willbe the e-keys that are logged as active. More specifically, if a husbandand wife wish to go to an even in the vehicle, and the wife is the firstto activate the vehicle using her e-keys, the e-keys used to activatethe vehicle will be the ones that are associated with the active use.

In one embodiment, if the user that activated the vehicle with his/here-keys does not proceed to drive or ride in the vehicle, the e-keys maybe disabled in a safe manner. Thus, in one embodiment, a backgroundsignal between the device used to activate the e-keys will communicatewith the vehicle to confirm that the device is in the vehicle. In oneembodiment, the background signal operates as a tether.

In still another embodiment, if a vehicle is stolen, the owner canaccess the website or app, and immediately cancel all e-keys for thevehicle. This will act to safely stop the vehicle, e.g., by slowing downthe vehicle if it is in motion, or lock the vehicle, report GPScoordinates, etc. The vehicle can, in one embodiment report activity,camera data, voice data, or any other monitoring data associated withthe condition that caused the e-keys to be violated.

In other embodiments, the vehicle can also participate and communicatewith the server of cloud services to perform either initial assignmentof the access codes, verification or monitoring.

Reporting data and history of use can also be logged separately for eache-key that is active or was active. As noted above, the e-keys can beassigned for particular privileges. In one embodiment, the privilegescan be assigned by selecting tick boxes, icons, drop down menus, timedurations, set limitations, conditions, etc. In some embodiments, atemplate can be provide for users. A template can have certainpredefined privileges that match the assignment of the e-keys. Forinstance, a template can be provide for a valet, a mechanic, a servicestore, a child, a spouse. The templates can be pre-defined by the systemand can also be adjusted or customized by the owner of the vehicle oradmin of the vehicle. Furthermore, although specific reference is madeto a vehicle, the embodiment can also be used for other types ofdevices, homes, structures, real estate lock boxes, lock boxes, safes,robots, electronics, etc.

The various embodiments may be embodied in computer readable media,which is saved in storage. The storage may be saved on cloud storage,data centers, or the like, which are accessible over the Internet. Theaccess may be wired or wireless. In vehicles, the connection to theInternet may be wireless, and the connection can be continuous ornon-continuous depending connection. Code on the vehicle electrons canexecute at least some of the method operations when not connected andother operations are executed jointly between vehicle electronics (e.g.,memory, code and processors of a vehicle) and cloud processing, whichmay implement one or more servers, either virtual or not.

It will be obvious, however, to one skilled in the art, that the presentinvention may be practiced without some or all of these specificdetails. In other instances, well known process operations have not beendescribed in detail in order not to unnecessarily obscure the presentinvention.

The various embodiments defined herein may define individualimplementations or can define implementations that rely on combinationsof one or more of the defined embodiments. Further, embodiments of thepresent invention may be practiced with various computer systemconfigurations including hand-held devices, microprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers and the like. The invention can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through awire-based or wireless network.

With the above embodiments in mind, it should be understood that theinvention could employ various computer-implemented operations involvingdata stored in computer systems. These operations are those requiringphysical manipulation of physical quantities. Usually, though notnecessarily, these quantities take the form of electrical or magneticsignals capable of being stored, transferred, combined, compared andotherwise manipulated.

Any of the operations described herein that form part of the inventionare useful machine operations. The invention also relates to a device oran apparatus for performing these operations. The apparatus can bespecially constructed for the required purpose, or the apparatus can bea general-purpose computer selectively activated or configured by acomputer program stored in the computer. In particular, variousgeneral-purpose machines can be used with computer programs written inaccordance with the teachings herein, or it may be more convenient toconstruct a more specialized apparatus to perform the requiredoperations.

The invention can also be embodied as computer readable code on acomputer readable medium. The computer readable medium is any datastorage device that can store data, which can thereafter be read by acomputer system. The computer readable medium can also be distributedover a network-coupled computer system so that the computer readablecode is stored and executed in a distributed fashion.

It should be understood that various examples are shown herein, and theexamples and figures should not limit a claimed embodiment to anyspecific example or figure. To the contrary, it should be understoodthat various embodiments are possible which can be made by combinedfeatures found in the illustrations, description and figures. Thus, someembodiments are possible for specific combinations of figures and partstaken from the various drawings, descriptions to define specificimplementations, as supported by the description. Additionally, any ofthe flow diagrams should not require any embodiments to include anyenumerated step, operation or order. Some operations may be taken indifferent orders from that show as examples in the figures, depending onthe desired implantation, as supported by the description.

Although the foregoing invention has been described in some detail forpurposes of clarity of understanding, it will be apparent that certainchanges and modifications can be practiced within the scope of theappended claims. Accordingly, the present embodiments are to beconsidered as illustrative and not restrictive, and the invention is notto be limited to the details given herein, but may be modified withinthe scope and equivalents of the description and claims.

What is claimed is:
 1. A method for generating service advice for a user account based on remotely obtained diagnostics data from a vehicle, comprising: receiving a request, at a server, to establish an advisor account for the vehicle associated with the user account, the request identifying a service entity and a vehicle service to be assigned to the service entity, the service entity is configured to receive said diagnostics data of the vehicle; associating, by the server, the advisor account to the service entity; sending, by the server, programming data to the vehicle, the programming data used by a computer of the vehicle to capture or collect select diagnostics data that relates to the vehicle service and said server is configured to make accessible said select diagnostics data to the advisor account for the service entity, the advisor account is made accessible to the service entity subsequent to establishing of the advisor account; and receiving, by the server, the select diagnostics data from the vehicle regarding the vehicle service, the select diagnostics data being accessible for viewing and/or processing by a device of the service entity, wherein the service entity is configured to use the select diagnostics data to send a message to the user account regarding a vehicle repair or a suggested vehicle repair determined using the select diagnostics data; wherein the user account is configured to establish a plurality of advisor accounts, each advisor account is associated with the vehicle and assigned to different aspects of the vehicle, each aspect of the vehicle is configured to receive select diagnostics data that relates to the aspect.
 2. The method of claim 1, wherein the vehicle service is related to a vehicle feature, or a vehicle function, or a vehicle operation or combinations thereof; and wherein the advisor account enables remote access to the select diagnostics data of the vehicle, the select diagnostics data being analyzed to determine if a service appointment is suggested for handling vehicle service or notification should be sent to the user account providing additional information or advice regarding the select diagnostics data.
 3. The method of claim 1, wherein the select diagnostics data produces updates that identify characteristics or changes in characteristics of the vehicle service that occur from time to time, and the server uses the identified characteristics or changes in characteristics to trigger a notification to the service entity regarding a problem or potential problem regarding the vehicle service.
 4. The method of claim 1, wherein the advisor account enables remote access to the select diagnostics data of the vehicle, the select diagnostics data being analyzed to determine if a service appointment is suggested for handling vehicle service or notification should be sent to the user account providing additional information or advice regarding the select diagnostics data.
 5. The method of claim 1, wherein the advisor account includes a communication protocol to enable a user of the advisor account to provide advice regarding the vehicle service based on the select diagnostics data, the advice based on analysis of historical failures or repairs for other vehicles having similar circumstances.
 6. The method of claim 1, wherein the advisor account is assigned with privileges that enable remote diagnostic of specific aspects of the vehicle that relate to the vehicle service, said remote diagnostics enabling remote advice regarding the vehicle service by the service entity, wherein said remote diagnostics implements one or more application programming interfaces (APIs).
 7. The method of claim 1, wherein advisor account defines a role that limits or enables access to one or more aspects of the vehicle, the advisor account may be for one of a dealer service entity, a dealership, a repair shop, a mechanic, a car service center, a private service, a tire service, an oil service, a friend, or an internet service.
 8. The method of claim 1, wherein access to said advisor account is enabled via a website or an application, the website or application provides user interfaces for creating accounts, or editing accounts, or viewing activity or history, or combinations thereof.
 9. The method of claim 1, wherein the vehicle service is for one or more of engine oil, engine light, oil pressure, battery status, electric powertrain status, phone lists, temperature, cooling system, charging system, radio settings, geo-location data, advisor history, tire rotation, tire heath, oil filter, battery, brake pads, brake systems, wipers, coolant, brake oil, transmission fluid, air filter, recall condition, broken part, service cycle, maintenance updates, part updates, advertisements regarding the vehicle, suggestions, or combinations of two or more thereof.
 10. A method for generating service advice for a user account based on remotely obtained diagnostics data from a vehicle, comprising: receiving a request, at a server, to establish an advisor account for the vehicle associated with the user account, the request identifying a service entity and a vehicle service to be assigned to the service entity, the service entity is configured to receive said diagnostics data of the vehicle; associating, by the server, the advisor account to the service entity; sending, by the server, programming data to the vehicle, the programming data used by a computer of the vehicle to store select diagnostics data that relates to the vehicle service and said server is configured to make accessible said select diagnostics data to the advisor account for the service entity, the advisor account is made accessible to the service entity subsequent to establishing of the advisor account; and receiving, by the server, the select diagnostics data from the vehicle regarding the vehicle service, the select diagnostics data being accessible for viewing and/or processing by a device of the service entity, wherein the select diagnostics data is used to identify characteristics or changes in characteristics that relate to the vehicle service, and the server uses the identified characteristics or changes in characteristics to trigger a notification to the service entity regarding a problem or potential problem regarding the vehicle service; wherein the user account is configured to establish a plurality of advisor accounts, each advisor account is associated with the vehicle and assigned to different aspects of the vehicle, each aspect of the vehicle is configured to receive select diagnostics data that relates to the aspect.
 11. The method of claim 10, wherein the vehicle service is related to a vehicle feature, or a vehicle function, or a vehicle operation or combinations thereof.
 12. The method of claim 10, wherein the advisor account enables remote access to the select diagnostics data of the vehicle, the select diagnostics data being analyzed to determine if a service appointment is suggested for handling vehicle service or notification should be sent to the user account providing additional information or advice regarding the select diagnostics data.
 13. The method of claim 10, wherein the advisor account includes a communication protocol to enable a user of the advisor account to provide advice regarding the vehicle service based on the select diagnostics data, the advice based on analysis of historical failures or repairs for other vehicles having similar circumstances.
 14. The method of claim 10, wherein the advisor account is assigned with privileges that enable remote diagnostic of specific aspects of the vehicle that relate to the vehicle service, said remote diagnostics enabling remote advice regarding the vehicle service by the service entity, wherein said remote diagnostics implements one or more application programming interfaces (APIs).
 15. The method of claim 10, wherein advisor account defines a role that limits or enables access to one or more aspects of the vehicle, the advisor account may be for one of a dealer service entity, a dealership, a repair shop, a mechanic, a car service center, a private service, a tire service, an oil service, a friend, or an Internet service.
 16. The method of claim 10, wherein access to said advisor account is enabled via a website or an application, the website or application provides user interfaces for creating accounts, or editing accounts, or viewing activity or history, or combinations thereof.
 17. The method of claim 10, wherein the vehicle service is for one or more of engine oil, engine light, oil pressure, battery status, electric powertrain status, phone lists, temperature, cooling system, charging system, radio settings, geo-location data, advisor history, tire rotation, tire heath, oil filter, battery, brake pads, brake systems, wipers, coolant, brake oil, transmission fluid, air filter, recall condition, broken part, service cycle, maintenance updates, part updates, advertisements regarding the vehicle, suggestions, or combinations of two or more thereof. 